Call this FIRST for the state of the MCP tool ecosystem in one shot: how many servers exist, how many actually answer a real handshake, how many are behind a login, the largest costume-farm concentration, AND the Tier-2 truth summary (how many server answers were re-derived against a public primary source and matched). Every number is re-derivable; grades observed/reported/derived. No arguments.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the transparency burden. It discloses that every number is re-derivable and that grades are observed/reported/derived, giving an honest picture of data provenance. The no-argument, read-only nature is implied by 'state... in one shot', though it does not explicitly rule out side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the 'Call this FIRST' directive and uses a compact, dense structure to enumerate all metrics. Every clause adds distinct value; there is no filler or redundancy, ending efficiently with 'No arguments'.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of an output schema, the description does a good job describing the expected metrics in prose (server counts, handshake answers, login barriers, costume-farm concentration, Tier-2 summary) and explains the grading approach. It is complete enough for an agent to know what the tool will return, though exact field names are not specified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters and the description explicitly states 'No arguments.' This matches the 100% schema-description coverage and the 0-param baseline, so the description adds no further parameter detail because none is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: provide a one-shot summary of the MCP tool ecosystem, including server counts, handshake success, login barriers, costume-farm concentration, and Tier-2 truth summary. The verb 'Call this FIRST' combined with the explicit list differentiates it from sibling tools like check_server and find_servers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Call this FIRST', giving clear precedence over sibling tools. It does not enumerate when not to use the tool or mention alternatives, but the 'first' guidance establishes a clear usage context for an initial high-level overview.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: should_i_use gives a quick verdict, check_server provides full evidence, find_tools searches by need, resolve_server_name handles name resolution, registry_pulse is a snapshot, changes_since is a diff, report_call sends feedback, and list_findings lists established findings. No two tools are easily confused.
Most tools follow a verb_noun pattern (check_server, find_tools, list_findings, report_call, resolve_server_name), but 'changes_since' and 'should_i_use' deviate, and 'registry_pulse' is noun_noun. The mixed conventions are still readable and predictable overall, but not perfectly uniform.
Eight tools is a well-scoped number for an observatory server. Each tool covers a distinct aspect of the lifecycle: discovery, decision, investigation, reporting, and ecosystem awareness. No tool feels redundant or missing.
The tool surface fully covers the verifier's domain: get a verdict (should_i_use), deep evidence (check_server), search by need (find_tools), resolve fuzzly names (resolve_server_name), ecosystem stats (registry_pulse), changes over time (changes_since), user feedback (report_call), and public findings (list_findings). There are no obvious gaps in the workflow.