SIGNL4 MCP by usefulapi: tool descriptions scored io.usefulapi/signl4

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

Scores, issues and names only

This page shows how SIGNL4 MCP by usefulapi (io.usefulapi/signl4)'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/signl4

Average score: 50.2 / 100Cloudy
Tools: 18
Near-identical descriptions: 0

Across the server

No server-wide issues.

Tools

signl4_get_duty_summary

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

signl4_get_alert_timeline

44 / 100Cloudy

Purpose: 14 / 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

signl4_get_duty_status

44 / 100Cloudy

Purpose: 14 / 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
Minor
Required identifiers whose description does not say where the value comes from: user_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

signl4_get_team

44 / 100Cloudy

Purpose: 14 / 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
Minor
Required identifiers whose description does not say where the value comes from: team_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

signl4_get_user

44 / 100Cloudy

Purpose: 14 / 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
Minor
Required identifiers whose description does not say where the value comes from: user_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

signl4_list_duty_schedules

46 / 100Cloudy

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

Minor
No `required` list, so every argument is optional.no_required
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

signl4_list_teams

47 / 100Cloudy

Purpose: 20 / 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

signl4_acknowledge_alert

50 / 100Cloudy

Purpose: 20 / 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
The description mentions none of its 3 or more arguments.params_not_in_description
Minor
Says nothing about what it returns.no_return_info

signl4_annotate_alert

50 / 100Cloudy

Purpose: 20 / 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

signl4_close_alert

50 / 100Cloudy

Purpose: 20 / 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
The description mentions none of its 3 or more arguments.params_not_in_description
Minor
Says nothing about what it returns.no_return_info

signl4_list_alerts

50 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 18 / 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
No `required` list, so every argument is optional.no_required
Minor
Says nothing about what it returns.no_return_info

signl4_list_categories

50 / 100Cloudy

Purpose: 20 / 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
Minor
Required identifiers whose description does not say where the value comes from: team_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

signl4_get_alert

52 / 100Cloudy

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

Minor
Says nothing about what it returns.no_return_info

signl4_list_team_users

52 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 20 / 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
No `required` list, so every argument is optional.no_required
Minor
Says nothing about what it returns.no_return_info

signl4_list_users

52 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 25 / 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

signl4_list_audit_logs

54 / 100Cloudy

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 17 / 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

signl4_get_alert_report

59 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 20 / 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
No `required` list, so every argument is optional.no_required

signl4_raise_alert

75 / 100Clear

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

Minor
The description mentions none of its 3 or more arguments.params_not_in_description
Minor
Required identifiers whose description does not say where the value comes from: team_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