Zoning Signal: tool descriptions scored com.zoningsignal/observatory

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

Scores, issues and names only

This page shows how Zoning Signal (com.zoningsignal/observatory)'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.zoningsignal/observatory

Average score: 74.6 / 100Clear
Tools: 18
Near-identical descriptions: 0

Across the server

No server-wide issues.

Tools

describe_zoning_signal

67 / 100Cloudy

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

list_corridors

67 / 100Cloudy

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

describe_corridor

69 / 100Cloudy

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

list_watch_items

71 / 100Clear

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

describe_watch

72 / 100Clear

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

No issues.

list_patterns

72 / 100Clear

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

describe_meeting

74 / 100Clear

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

No issues.

describe_place

74 / 100Clear

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

No issues.

get_track_record

74 / 100Clear

Purpose: 20 / 20
When to use: 10 / 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

list_entities

74 / 100Clear

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

submit_agent_feedback

74 / 100Clear

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 22 / 25
Return value: 15 / 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
The description mentions none of its 3 or more arguments.params_not_in_description

meeting_index

75 / 100Clear

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

No issues.

describe_pattern

77 / 100Clear

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

No issues.

list_places

79 / 100Clear

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

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

trace_connection

79 / 100Clear

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

Minor
The description is long (524 words). It helps selection but costs steps and tokens.too_long

semantic_search

80 / 100Clear

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

Minor
The description says the tool is deprecated. Name the replacement, and consider taking the tool out of tools/list: models avoid it when asked for what it does.deprecated

describe_entity

82 / 100Clear

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

No issues.

list_meetings

82 / 100Clear

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

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

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