Skip to main content
Glama

A town's climate by month

get_climate
Read-onlyIdempotent

A town's climate: a one-line summary and a paragraph, the 12 monthly averages (high, low, rain, humidity, sun), the most and least pleasant months, a 0–100 nice-weather score, cost of living when known, and links. Temperatures in °C and °F, rain in mm and inches.

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

Input Schema

NameRequiredDescriptionDefault
placeYesTown name ("Lisbon", "Portland, Oregon"), Climatch slug ("portland-oregon") or GeoNames id. The most populous match wins

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real context the annotations cannot: exactly what the response contains, that values come in both metric and imperial units, and that cost of living is only present 'when known' - a useful partial-data caveat. It stops short of describing failure or ambiguity behavior, which the schema covers instead.

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 sentences, front-loaded with the headline deliverable and then the full payload list, with a short unit-disambiguation sentence at the end. The enumeration is dense but every item earns its place given there is no output schema; only minor trimming would be possible.

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 carries the return-value burden and discharges it well by listing all fields and units. For a single-parameter, read-only lookup this is nearly complete; only edge-case behavior (no match, ambiguous place) is left implicit in the schema.

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?

Schema coverage is 100% and the single 'place' parameter is fully documented in the schema, including accepted formats and the most-populous-match tiebreak rule. The description adds no parameter-level meaning, so the baseline 3 applies.

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 a specific resource and scope: a single town's month-by-month climate, with the exact payload enumerated (12 monthly averages, best/worst months, 0-100 score, cost of living, links). It never names a sibling, so an agent must infer from the sibling list that single-town lookup is distinct from compare_climates or best_weather_in_month, but the payload list itself makes the difference fairly evident.

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: an agent can infer this is the tool for 'what is the climate like in X', but there is no explicit when-to-use clause, no mention of when to prefer compare_climates or best_weather_in_month, and no statement about the single-place constraint. Adequate but with a clear routing gap.

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