Skip to main content
Glama

climate

smoke_by_month

Returns the 12 monthly PM2.5 air-quality averages and their bands (clear, hazy, smoky, very smoky) for 20 nomad bases in Asia and Mexico, such as Chiang Mai, Hanoi and Bangkok.

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": {
      "place": "<place>"
    },
    "name": "smoke_by_month"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesPlace name, e.g. "Chiang Mai"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the returned payload (12 monthly averages plus four named band categories), which is real behavioral context. However, it says nothing about what happens if 'place' is not one of the 20 supported bases (error, empty result, fuzzy match), or any auth/rate-limit characteristics.

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?

One sentence, zero filler, with the returned payload front-loaded and the geographic scope and examples following. Nothing could be removed without losing information.

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 single-parameter read-only lookup with no annotations or output schema, the description covers what is returned and what values are valid. The remaining gap is the behavior for unsupported place names, which matters for an agent that may pass an arbitrary city.

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 would be 3, but the description adds meaning: the 'place' value is constrained to 20 nomad bases in Asia and Mexico, and it supplies concrete valid examples (Chiang Mai, Hanoi, Bangkok). That constrains the parameter's domain beyond the schema's single example.

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 a specific verb and resource ('Returns the 12 monthly PM2.5 air-quality averages and their bands') and constrains scope to 20 nomad bases in Asia and Mexico with concrete examples. It never names the siblings climate_by_month or best_months, so the agent must infer the boundary between air-quality data and climate/best-month data.

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?

The description states what data is returned but gives no when-to-use guidance, no conditions under which another tool (e.g. climate_by_month or best_months) is the better choice, and no prerequisites. The use case for PM2.5 bands is only implied by the subject matter.

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