Skip to main content
Glama
Sign In

PourWire

by com.pourwire
OverviewDiscussionsAdmin

Metro opening stats

metro_stats
Read-only

Summary stats for a metro: tracked venues, new this week, sources.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "metro": "<metro>"
    },
    "name": "metro_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
metroYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / metro / enum
      Previous value: -[
-  "los-angeles",
-  "new-york",
-  "westchester",
-  "long-island",
-  "austin",
-  "waco-temple",
-  "dallas-fort-worth",
-  "houston",
-  "san-antonio",
-  "phoenix",
-  "chicago-suburbs",
-  "raleigh",
-  "charlotte",
-  "greensboro",
-  "miami",
-  "tampa",
-  "orlando",
-  "fairfield-ct"
-]New value: +[
+  "los-angeles",
+  "new-york",
+  "westchester",
+  "long-island",
+  "hudson-valley",
+  "capital-region",
+  "rochester",
+  "buffalo",
+  "austin",
+  "waco-temple",
+  "dallas-fort-worth",
+  "houston",
+  "san-antonio",
+  "phoenix",
+  "chicago-suburbs",
+  "raleigh",
+  "charlotte",
+  "greensboro",
+  "miami",
+  "tampa",
+  "orlando",
+  "fairfield-ct"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / metro / enum
      Previous value: -[
-  "los-angeles",
-  "new-york",
-  "westchester",
-  "long-island",
-  "austin",
-  "waco-temple",
-  "dallas-fort-worth",
-  "houston",
-  "san-antonio",
-  "phoenix",
-  "chicago-suburbs",
-  "raleigh",
-  "charlotte",
-  "greensboro",
-  "miami",
-  "tampa",
-  "orlando"
-]New value: +[
+  "los-angeles",
+  "new-york",
+  "westchester",
+  "long-island",
+  "austin",
+  "waco-temple",
+  "dallas-fort-worth",
+  "houston",
+  "san-antonio",
+  "phoenix",
+  "chicago-suburbs",
+  "raleigh",
+  "charlotte",
+  "greensboro",
+  "miami",
+  "tampa",
+  "orlando",
+  "fairfield-ct"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / metro / enum
      Previous value: -[
-  "los-angeles",
-  "new-york",
-  "westchester",
-  "long-island",
-  "austin",
-  "waco-temple",
-  "dallas-fort-worth",
-  "houston",
-  "san-antonio",
-  "phoenix",
-  "chicago-suburbs",
-  "raleigh",
-  "charlotte"
-]New value: +[
+  "los-angeles",
+  "new-york",
+  "westchester",
+  "long-island",
+  "austin",
+  "waco-temple",
+  "dallas-fort-worth",
+  "houston",
+  "san-antonio",
+  "phoenix",
+  "chicago-suburbs",
+  "raleigh",
+  "charlotte",
+  "greensboro",
+  "miami",
+  "tampa",
+  "orlando"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / metro / enum
      Previous value: -[
-  "los-angeles",
-  "new-york",
-  "westchester",
-  "long-island",
-  "austin",
-  "waco-temple",
-  "dallas-fort-worth",
-  "houston",
-  "san-antonio",
-  "phoenix",
-  "chicago-suburbs"
-]New value: +[
+  "los-angeles",
+  "new-york",
+  "westchester",
+  "long-island",
+  "austin",
+  "waco-temple",
+  "dallas-fort-worth",
+  "houston",
+  "san-antonio",
+  "phoenix",
+  "chicago-suburbs",
+  "raleigh",
+  "charlotte"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / metro / enum
      Previous value: -[
-  "los-angeles",
-  "new-york",
-  "westchester",
-  "long-island",
-  "austin",
-  "waco-temple",
-  "dallas-fort-worth",
-  "houston",
-  "san-antonio",
-  "phoenix"
-]New value: +[
+  "los-angeles",
+  "new-york",
+  "westchester",
+  "long-island",
+  "austin",
+  "waco-temple",
+  "dallas-fort-worth",
+  "houston",
+  "san-antonio",
+  "phoenix",
+  "chicago-suburbs"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / metro / enum
      Previous value: -[
-  "los-angeles",
-  "new-york",
-  "austin",
-  "waco-temple",
-  "dallas-fort-worth",
-  "houston",
-  "san-antonio",
-  "phoenix"
-]New value: +[
+  "los-angeles",
+  "new-york",
+  "westchester",
+  "long-island",
+  "austin",
+  "waco-temple",
+  "dallas-fort-worth",
+  "houston",
+  "san-antonio",
+  "phoenix"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / metro / enum
      Previous value: -[
-  "los-angeles",
-  "new-york",
-  "austin",
-  "waco-temple",
-  "dallas-fort-worth",
-  "houston",
-  "san-antonio"
-]New value: +[
+  "los-angeles",
+  "new-york",
+  "austin",
+  "waco-temple",
+  "dallas-fort-worth",
+  "houston",
+  "san-antonio",
+  "phoenix"
+]
  8. First observed

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish readOnlyHint and openWorldHint, and the description adds the content of the summary (tracked venues, new this week, sources). It does not explain freshness, what 'new this week' means, permissions, or response format, so it adds only moderate behavioral context.

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?

The description is a single front-loaded sentence with no filler, and the colon list efficiently enumerates the stats. Every phrase contributes to the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read-only tool, the description covers the core stats but does not define them or describe the return shape, which matters because there is no output schema. The absence of sibling routing and parameter details leaves gaps for an agent choosing and calling the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single metro parameter, and the description merely repeats 'for a metro' without explaining the enum slugs, how to choose a metro, or validation behavior. The schema enum supplies allowed values, but the description does not compensate for the missing parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the resource (metro) and the specific stats returned (tracked venues, new this week, sources), so the purpose is clear. It does not distinguish itself from the sibling search_openings, which is the only gap under this dimension.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no mention of search_openings as an alternative, and no exclusions or prerequisites. The purpose implies it is for summary stats, but the definition leaves selection between this and search_openings to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PourWire toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources