Skip to main content
Glama

climate

climate_by_month

Returns the 12 monthly climate averages (high and low °C, rain mm, rain days, cloud %, humidity %) for one place among about 100 digital nomad bases worldwide.

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

Input Schema

NameRequiredDescriptionDefault
placeYesPlace name, e.g. "Lisbon" or "Chiang Mai, Thailand"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 burden, and it does disclose the returned metric set and the coverage limitation of ~100 bases. It does not say what happens with an unrecognized or ambiguous place string (error vs. fuzzy match vs. empty result), which is the key behavioral unknown for a free-text lookup.

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, front-loaded with the return value and then the scope constraint, with zero filler. Every clause contributes information an agent needs.

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 one-parameter read tool with no output schema, the description specifies the return contents well enough to use the result without further explanation. The only missing piece is failure/ambiguity behavior for unmatched place names, which is a minor gap at this complexity level.

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?

The single 'place' parameter is fully documented in the schema (100% coverage), so the baseline is 3. The description adds real meaning beyond the schema by revealing that only ~100 digital nomad bases are valid inputs, telling the agent to expect restricted coverage rather than arbitrary geographies.

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 ('Returns the 12 monthly climate averages') and enumerates exactly which metrics come back (high/low °C, rain mm, rain days, cloud %, humidity %). It also bounds scope to 'one place among about 100 digital nomad bases worldwide,' which implicitly separates it from best_months. It never explicitly contrasts with a sibling, so it lands just short of a 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?

Usage is only implied: an agent can infer this is the tool for raw monthly climate figures for a single location. There is no explicit when-to-use/when-not guidance and no pointer to best_months for month selection or smoke_by_month for air quality, both of which are adjacent needs an agent might confuse.

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