Metros
metrosRead-onlyIdempotent
List the metros DoStuff covers (slug + name). Pass a slug to the events tool.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Dostuff
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly, idempotent, non-destructive. Description adds that it returns slug and name, no contradiction. Provides context that output feeds events tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise with two sentences, no filler, front-loaded with purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and no output schema, description fully explains tool's function and how to use its output. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters; schema coverage is 100%. Baseline 4 applies; no additional parameter info needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses specific verb 'List' and resource 'metros DoStuff covers' with details (slug + name). Also distinguishes from sibling tools by mentioning usage with 'events' tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Clearly states the tool lists available metros and suggests passing slug to events tool for further use. Could explicitly mention when not to use, but good overall.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.8/5.0
Disambiguation2/5
The set contains near-duplicate tools (ask_pipeworx_beta explicitly 'currently matches ask_pipeworx exactly') and a dense family of six polymarket_* tools whose boundaries are subtle, plus overlapping onboarding tools in discover_tools and suggest_questions. Detailed descriptions mitigate some confusion, but several tools are difficult to tell apart without reading their full text.
Naming Consistency3/5
All names are lowercase snake_case and readable, with consistent prefix families (ask_pipeworx, polymarket_, pipeworx_), but the overall structure is mixed: bare verbs (remember, forget, subscribe), adjective+noun names (recent_alerts, recent_changes), and noun+noun domain tags (polymarket_edges, entity_profile) rather than a uniform verb_noun pattern.
Tool Count2/5
At 33 tools the set exceeds the 25-tool threshold and feels heavy, carrying an experimental duplicate of ask_pipeworx and a six-tool polymarket family that could plausibly be consolidated. The breadth reflects several unrelated domains bundled into one server rather than a focused scope.
Completeness3/5
The data-research core (ask, grounded, deep_research, profiles, comparisons, claim validation, entity resolution) and the prediction-market analysis suite are thoroughly covered, and memory plus subscription lifecycles are complete. However, the events domain the server is named for is thin (only events + metros), and the overall set lacks a single coherent purpose against which completeness can be cleanly judged.