CitySignal AI: tool descriptions scored com.citysignalai/citysignal

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

Scores, issues and names only

This page shows how CitySignal AI (com.citysignalai/citysignal)'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/com.citysignalai/citysignal

Average score: 69.4 / 100Cloudy
Tools: 23
Near-identical descriptions: 0

Across the server

Minor
The server's instructions are 3049 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

city_events

50 / 100Cloudy

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

Major
Arguments without a description: days, limit.param_no_description
Minor
No `required` list, so every argument is optional.no_required

get_profile

54 / 100Cloudy

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

city_cameras

58 / 100Cloudy

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

Major
Arguments without a description: lat, lon, radius_mi, hours.param_no_description

get_signal

58 / 100Cloudy

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

Minor
Arguments without a description: signal_id.param_no_description
Minor
Required identifiers whose description does not say where the value comes from: signal_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

city_week

62 / 100Cloudy

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

Minor
No `required` list, so every argument is optional.no_required

list_cities

62 / 100Cloudy

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

No issues.

city_near

63 / 100Cloudy

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

Minor
Arguments without a description: lat, lon, radius_mi.param_no_description

my_brief

67 / 100Cloudy

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

No issues.

my_spots_and_routes

67 / 100Cloudy

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

No issues.

get_detour

70 / 100Clear

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

No issues.

circle_along_the_way

72 / 100Clear

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

Minor
Arguments without a description: day.param_no_description
Minor
No `required` list, so every argument is optional.no_required

city_incidents

72 / 100Clear

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

Minor
No `required` list, so every argument is optional.no_required

my_along_the_way

72 / 100Clear

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

No issues.

my_day

72 / 100Clear

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

No issues.

my_list

72 / 100Clear

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

No issues.

my_routes_now

72 / 100Clear

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

No issues.

circle_needs

75 / 100Clear

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

Minor
No `required` list, so every argument is optional.no_required

city_now

76 / 100Clear

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

Minor
No `required` list, so every argument is optional.no_required

my_detours

77 / 100Clear

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

No issues.

save_spot

77 / 100Clear

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

No issues.

cities_report

80 / 100Clear

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

Minor
No `required` list, so every argument is optional.no_required

city_pictures

82 / 100Clear

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

Minor
No `required` list, so every argument is optional.no_required

add_errand

87 / 100Clear

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

No issues.

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