Skip to main content
Glama

climate

best_months

Returns the top 3 months for dry, warm, cool, sunny or clean-air weather in one place among about 100 digital nomad bases worldwide, with the numbers and the rule used.

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>",
      "what": "<what>"
    },
    "name": "best_months"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatYesWhat to optimise for. clean-air only exists for 20 places.
placeYesPlace name, e.g. "Hanoi"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose that results come with the underlying numbers and the selection rule used, which is valuable methodology transparency, plus the ~100-place dataset limit. However, it says nothing about what happens when a place is outside that set, and the clean-air restriction to 20 places lives only in the schema, not the prose.

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?

A single dense sentence with the outcome and the scope front-loaded, and no filler. It is slightly packed, stacking the criteria list and dataset scope together, but every clause carries 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 two-parameter, fully documented, non-mutating lookup with no output schema, the description covers purpose, ranking behavior, result contents, and dataset scope. The main remaining gap is failure behavior for uncovered or misspelled places.

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 the baseline is 3, and the description does add meaning: it enumerates the same five criteria as a weather-optimisation choice and constrains 'place' to the ~100 supported bases. It reinforces rather than duplicates, without adding format or matching details beyond the enum.

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 verb and resource: it returns the top 3 months for a named weather criterion at one place, drawn from ~100 digital nomad bases. The ranking framing ('top 3 months ... with the numbers and the rule used') separates it from a plain monthly climate lookup, though it never names climate_by_month or smoke_by_month as alternatives.

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 phrase 'in one place among about 100 digital nomad bases worldwide' implicitly tells the agent this is a single-place, single-criterion lookup restricted to a fixed dataset, which is useful scope guidance. There is no explicit statement of when to prefer it over climate_by_month or smoke_by_month, so selection is left to inference from sibling names.

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