Skip to main content
Glama

AutoTasker Hub — China Social Data API

air_quality

Air quality + PM2.5/PM10/European AQI for any city or lat/lon (Open-Meteo). China cities supported. $0.01 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "air_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
cityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description bears the full burden. It usefully discloses the upstream provider and the per-call price ($0.01 USDC), which is real behavioral context, but says nothing about whether city names are geocoded server-side, what happens if both city and lat/lon are supplied, or whether partial coordinates are tolerated. Overall mutation/read semantics, failure behavior and result shape stay undisclosed.

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?

Three short fragments, front-loaded with the resource and measurements, followed by coverage and price. Little waste, though the parenthetical source and the price tag are appended rather than integrated, and the fragment style makes the input-mode note slightly ambiguous.

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 three-parameter read tool with no output schema, the description covers what is returned, where data comes from, coverage and cost. The meaningful gap is parameter interaction (city vs. lat/lon) and any note on response granularity or time reference, which an agent needs in order to call it correctly the first time.

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 coverage is 0% and the description only gestures at the parameters via 'any city or lat/lon'. It never explains that lat and lon are separate numeric fields, whether they must be supplied together, whether city overrides coordinates, or what city string format (English vs. Chinese name) is expected. All three parameters effectively lack meaning beyond their names.

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 and the specific measurements returned (PM2.5, PM10, European AQI), the upstream source (Open-Meteo), and the accepted location forms. It is clearly a read/retrieval tool for any city or coordinate. It does not differentiate from related siblings such as carbon_intensity, so it stops short of a 5.

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?

Usage is implied rather than stated: 'for any city or lat/lon' tells the agent it should reach for this when it has a place name or coordinates. There is no explicit when-to-use/when-not guidance and no mention of alternatives for air-quality-adjacent data. The 'China cities supported' note is useful context but not a routing rule.

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.