Skip to main content
Glama

A city's daily history

city_history
Read-only

A measured city's daily mean PM2.5 (its local calendar days, µg/m³) and its daily rank, between two dates (up to 400 days; default the last 30), with monthly means. Also a city measured only in the past, or a day late (Georgia's national network), with no rank.

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": "city_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD, default yesterday
cityYesCity as its page path ("us/los-angeles"), a SmogRank URL, or a name ("Lahore", "Delhi, India"). find_city lists the paths.
fromNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly annotations, it discloses real behavioral traits: a 400-day maximum window, a default of the last 30 days, inclusion of monthly means, possible absence of rank for certain cities, and data latency ('a day late'). That materially helps an agent predict response shape and failure cases. It doesn't describe pagination or output format, but annotations are minimal here so the description carries most of the load well.

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?

Two dense sentences, front-loaded with the resource and unit before the constraints. The trailing fragment about past-only/day-late cities is awkwardly elliptical and costs some readability, but no clause is padding — each adds scope, limits, or a caveat.

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?

With no output schema, the description must convey returns, and it does: daily means, daily rank, and monthly means, including the case where rank is absent. Units and date-window limits are covered. What's missing is only return structure/format detail, which is a minor gap for a read-only query tool.

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?

Schema coverage is 100%, so baseline is 3, but the description adds the 400-day cap and the default 30-day window that the schema does not state, plus the µg/m³ unit context. The `to` default of 'yesterday' is already in the schema, so that part is redundant. Net gain above the schema is real but modest.

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?

The description names the exact resource and measures: a city's daily mean PM2.5 (µg/m³) plus daily rank over a date range, with monthly means. It also carves out an edge case (past-only or day-late cities with no rank). It stops short of explicitly contrasting itself with city_air or rankings, so the sibling boundary is only partly drawn.

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

Usage Guidelines3/5

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

It gives a routing hint by pointing to find_city for city paths, and implies the historical/daily use case. But it never says when to prefer this over city_air (current conditions?) or rankings (aggregate ranks), and no explicit exclusions are stated. Usage is implied rather than directed.

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.

Resources