Skip to main content
Glama

Where the weather is best in a month

best_weather_in_month
Read-onlyIdempotent

The 30 large towns with the most comfortable weather in a month (afternoon highs near 24°C / 75°F, little rain, low humidity), spread across countries. From the ~2,000 most populous towns.

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": {
      "month": "<month>"
    },
    "name": "best_weather_in_month"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYesMonth, 1 = January … 12 = December
countryNoOnly this ISO country code

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?

Annotations already declare read-only, non-open-world, idempotent behavior, so the bar is lower. The description still adds real context: a hard cap of 30 results, the exact comfort thresholds used for ranking, and the population universe the towns are drawn from — all of which shape how an agent should interpret and present results.

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?

A single sentence that front-loads the result count and the ranking concept, then supplies the criteria and the candidate pool in parentheses. No filler, no repetition of the title, nothing to cut.

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 two-parameter read-only query with full schema coverage and no output schema, the definition supplies enough: what is returned, how many, how ranked, and over what universe. The main remaining gap is how the country filter combines with the 30-result limit and whether results are ordered.

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 both parameters are already documented with range and ISO-code pattern, so the schema carries the burden. The description adds nothing about month or country semantics beyond what is structured — notably it doesn't say whether country restricts the ranking to towns in that country or how it interacts with the 30-result cap.

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?

States a specific resource (the 30 large towns with the most comfortable weather in a month) and pins the ranking criteria (afternoon highs near 24°C, little rain, low humidity) plus the candidate pool (~2,000 most populous towns). That is far more concrete than a name restatement. It does not explicitly name a sibling it is distinct from, so it stops short of 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?

The description implies the use case (ranking places by comfort for a given month) but never says when to choose this over compare_climates, find_similar_climates, or weather_for_the_money, and gives no exclusions or prerequisites. The guidance is inferable rather than stated.

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