Uptimepage: tool descriptions scored dev.uptimepage/uptimepage

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://mcp.uptimepage.dev/mcp
Homepage: uptimepage.dev/mcp-server
Repository: github.com/uptimepage/uptimepage
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how Uptimepage (dev.uptimepage/uptimepage)'s tool descriptions scored, the issues found and the names of its tools and parameters. The descriptions are the server's own: read them where the copy came from.

Forecall asked the URL this server lists in the official MCP Registry for its tools/list once, on the date above, without calling any tool. The server may have changed since.

servers/dev.uptimepage/uptimepage

Average score: 64.8 / 100Cloudy
Tools: 41
Near-identical descriptions: 2

Across the server

Major
41 tools. Above 40, models choose less accurately.too_many_tools
Minor
The server's instructions are 3116 characters. Claude Code reads only the first 2,048 by default (Codex 0.154.0 reads them whole). Put what the server is for first.instructions_long

Tools whose descriptions are nearly the same

2 of 2 pairs shown, highest description similarity first.
Tool	Tool	Description similarity	Name similarity
acknowledge_incident	resolve_incident	0.61	0.33
update_monitor	update_monitor_group	0.45	0.67

Tools

acknowledge_incident

53 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 0 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Its description is nearly the same as resolve_incident's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use resolve_incident instead.confusable_pair
Minor
String arguments with no constraint or example: id.loose_string_param

get_incident_metrics

55 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 0 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
No `required` list, so every argument is optional.no_required

resolve_incident

56 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 0 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Its description is nearly the same as acknowledge_incident's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use acknowledge_incident instead.confusable_pair
Minor
String arguments with no constraint or example: id.loose_string_param
Minor
Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

get_maintenance

57 / 100Cloudy

Purpose: 14 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

update_status_page_component

57 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 12 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Arguments without a description: public_description, public_name, sort_order.param_no_description

get_incident

58 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

update_status_page

58 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 0 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

get_status_page

60 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

list_monitors

60 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
No `required` list, so every argument is optional.no_required

list_notification_channels

60 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 0 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

list_status_pages

60 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
No `required` list, so every argument is optional.no_required

update_monitor

60 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Its description is nearly the same as update_monitor_group's (similarity 0.45); only the names and schemas tell them apart. Say in this description when to use update_monitor_group instead.confusable_pair

post_incident_update

61 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
String arguments with no constraint or example: id.loose_string_param
Minor
Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

resume_monitor

61 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

unpublish_incident

61 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

get_org_health

62 / 100Cloudy

Purpose: 14 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

get_flow_runs

63 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

No issues.

get_flow_step_trend

63 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

No issues.

get_monitor_history

63 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

get_org_usage

63 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 0 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

list_status_page_viewers

63 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

post_maintenance_update

63 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

set_monitor_state

63 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 15 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Arguments without a description: state.param_no_description

update_maintenance

63 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

list_maintenance

65 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 22 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
No `required` list, so every argument is optional.no_required

list_monitor_groups

65 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

list_tags

65 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

update_monitor_group

65 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Its description is nearly the same as update_monitor's (similarity 0.45); only the names and schemas tell them apart. Say in this description when to use update_monitor instead.confusable_pair

pause_monitor

66 / 100Cloudy

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

No issues.

publish_incident

66 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
String arguments with no constraint or example: id.loose_string_param

create_status_page

68 / 100Cloudy

Purpose: 20 / 20
When to use: 10 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 0 / 10

No issues.

list_incidents

68 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
No `required` list, so every argument is optional.no_required

get_monitor

70 / 100Clear

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 18 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

No issues.

add_status_page_components

71 / 100Clear

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

cancel_maintenance

73 / 100Clear

Purpose: 20 / 20
When to use: 10 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

No issues.

run_check_now

73 / 100Clear

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

list_variables

75 / 100Clear

Purpose: 17 / 20
When to use: 10 / 20
Arguments: 25 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

No issues.

create_monitors

76 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 0 / 10

No issues.

list_regions

80 / 100Clear

Purpose: 17 / 20
When to use: 15 / 20
Arguments: 25 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

No issues.

create_maintenance

83 / 100Clear

Purpose: 20 / 20
When to use: 20 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 5 / 10

No issues.

create_monitor

84 / 100Clear

Purpose: 20 / 20
When to use: 10 / 20
Arguments: 19 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Minor
Arguments without a description: check.param_no_description

What static scoring cannot tell

This score reads only the text of each description and schema: it says what is written, not what a model will do. Short tools whose names already say what they do, such as browser_close, score low here even when models use them well, and in our measurements current models chose the right tool in one step even from one-line descriptions, as long as the names and schemas differed. What the text cannot show, such as what happens over several steps and whether an added sentence helps or misleads, is what an evaluation measures, on the Pro and Team plans.

Is your server listed here and you would rather it were not? Email support@forecall.dev, and we will take it off within 7 days.

All scored servers