Skip to main content
Glama

Compare two towns' climates

compare_climates
Read-onlyIdempotent

Two towns side by side: their 0–100 climate match, a few sentences on how they differ, and both sets of monthly averages. When seasonsFlipped, B's months are shifted 6 in alignedB so July lines up with January. 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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "compare_climates"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesFirst town
bYesSecond town

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description correctly spends its words elsewhere: return contents, the hemisphere-alignment behavior of alignedB, and the dual unit conventions (°C/°F, mm/inches). The only weak point is that seasonsFlipped is referenced as if it were a switch on this call when the schema exposes only a and b.

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 tight sentences, with the payload described first and edge behavior and units second, so nothing is buried. The seasonsFlipped clause is the one piece that costs the reader more than it returns, since no such argument exists.

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 burden of explaining returns and does so (match score, prose differences, monthly averages, units). The dangling seasonsFlipped/alignedB reference is the remaining incompleteness, since it describes a mode the agent cannot actually request.

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%, so the two town parameters are already documented and the baseline is 3. The description adds that b is the 'B' whose months shift in alignedB, which clarifies the asymmetric role of the second parameter, but the seasonsFlipped reference introduces a parameter concept absent from the schema.

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 states concretely what the tool produces: a 0-100 climate match, a few sentences on differences, and both sets of monthly averages. That is unmistakably a pairwise comparison, distinct from single-place lookups like get_climate, though it never names a sibling to route against.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named, so an agent must infer from the tool name whether this beats find_similar_climates or two separate get_climate calls. The only conditional statement concerns seasonsFlipped, which is not a parameter here.

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