Forecall
Failure recordsDocs
All scored servers

NodePing MCP by usefulapi: tool descriptions scored io.usefulapi/nodeping

tools/list taken
(UTC)
From
Official MCP Registry
Connected to
https://nodeping.usefulapi.io/mcp
Homepage
usefulapi.io/nodeping/
Repository
github.com/m190/usefulapi-mcp
Scoring rules
v2
Removal
support@forecall.dev
Score this URL as it is today

Scores, issues and names only

This page shows how NodePing MCP by usefulapi (io.usefulapi/nodeping)'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/io.usefulapi/nodeping
Average score
48.8 / 100Cloudy
Tools
28
Near-identical descriptions
0

Across the server

  • Minor
    28 tools. Above 25, models start to tell tools apart less well.many_tools

Tools

nodeping_delete_maintenance

39 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    The description only restates the name (9 words).restates_name
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: maintenance_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_get_account

41 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 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
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_get_maintenance

41 / 100Cloudy

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    The description only restates the name (8 words).restates_name
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: maintenance_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_list_contact_groups

41 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 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
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_list_maintenance

41 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 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
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_list_notification_profiles

41 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 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
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_list_schedules

41 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 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
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_create_contact_group

42 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
18 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: name.param_no_description
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_create_adhoc_maintenance

44 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
17 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: name, check_ids.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: check_ids. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_list_contacts

44 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 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
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_delete_schedule

46 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 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
    Says nothing about what it returns.no_return_info

nodeping_get_probe_info

47 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_update_contact_group

48 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
19 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: name.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: group_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_get_schedule

49 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_delete_contact_group

50 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 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
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: group_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_get_current_events

51 / 100Cloudy

Purpose
14 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_get_check_results

52 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: check_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_get_check_summary

52 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 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
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: check_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_get_check_uptime

52 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: check_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_get_contact

54 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: contact_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_list_notifications

54 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_disable_check

55 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: check_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_mute_check

55 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: check_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_get_check

56 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
7 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    The meaning of the boolean argument uptime is unclear.vague_boolean
  • Minor
    Required identifiers whose description does not say where the value comes from: check_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_update_check

56 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
21 / 25
Return value
0 / 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
    Arguments without a description: label.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: check_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

nodeping_list_checks

57 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_put_schedule

58 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
21 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Arguments without a description: monday, tuesday, wednesday, thursday, friday, saturday, sunday.param_no_description
  • Minor
    The meaning of the boolean argument monday.allday is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument tuesday.allday is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument wednesday.allday is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument thursday.allday is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument friday.allday is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument saturday.allday is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument sunday.allday is unclear.vague_boolean
  • Minor
    Says nothing about what it returns.no_return_info

nodeping_get_check_events

59 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
7 / 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
    Arguments without a description: limit.param_no_description
  • Minor
    Required identifiers whose description does not say where the value comes from: check_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

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