Skip to main content
Glama
city-data-mcp

city-data-mcp

Official

Track City Changes Over Time

track_city_changes

Monitor a city's momentum by pulling trend data on unemployment, economics, crime, permits, and 311 complaints from BLS, FRED, FBI. Get a dashboard marking each metric improving, declining, or stable.

Instructions

Show how a city is changing — what's improving, declining, or holding steady. Pulls trend data from BLS (unemployment), FRED (economics), FBI (crime), building permits, and 311 complaints.

Returns a directional dashboard: each metric tagged as improving, declining, or stable with supporting data. Great for spotting momentum or emerging problems.

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": {
      "city": "<city>"
    },
    "name": "track_city_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name (e.g., 'Denver', 'Austin', 'NYC')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries full burden and does meaningful work: it discloses the underlying data sources, the return structure (per-metric improving/declining/stable tags), and the analytical framing. It omits anything about auth requirements, rate limits, latency, or data freshness, which are the remaining gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then supporting sources, then output shape. Mostly earns its place, though 'Great for spotting momentum or emerging problems' is soft marketing filler that a stricter version would cut.

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

Completeness4/5

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

For a one-parameter read-only aggregate with no output schema and no annotations, the description gives enough: what it aggregates, what it returns, and the directional tagging scheme. Only the absence of any data-source caveats or freshness notes keeps it from 5.

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

Parameters3/5

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

Single parameter with 100% schema description coverage, so the schema already documents 'city' fully with examples. The description adds nothing about city syntax (e.g., supported formats, whether metro areas count), so baseline 3 applies.

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?

States a specific verb+resource ('show how a city is changing') and immediately names the aggregation scope — BLS, FRED, FBI, permits, 311 — which distinguishes it from the single-domain siblings like query_employment or query_311_trends. The output shape ('directional dashboard') is also stated, so an agent can tell what it gets without opening a schema.

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?

Gives clear context ('spotting momentum or emerging problems'), which tells the agent this is a trend/aggregate tool rather than a raw-data query. However, it never names an alternative or states a when-not condition (e.g., use query_city_data for raw values), so the exclusion guidance is absent.

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