Skip to main content
Glama

Places with a climate like a town

find_similar_climates
Read-onlyIdempotent

Towns whose climate is most like a town's, best match first, optionally 'but warmer / cooler / drier / sunnier / less humid', for one month, or within some countries or continents. Each match has its 0–100 score, how it differs, and links. Defaults match the Climatch app: year-round, abroad only, 25,000+ people.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax matches. Default 10
monthNoCompare one calendar month only (e.g. where is July like Lisbon's July). Default: the whole year
placeYesTown name ("Lisbon", "Portland, Oregon"), Climatch slug ("portland-oregon") or GeoNames id. The most populous match wins
adjustNoLike the place, but… Stack freely, except warmer with cooler
countriesNoOnly these ISO country codes, e.g. ["ES","PT"]
continentsNoOnly these continents: AF AS EU NA OC SA
min_populationNoSmallest town to list. Default 25000
exclude_home_countryNoLeave out the place's own country. Default true

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 readOnly, idempotent, and closed-world, so safety is covered; the description adds real behavioral context beyond that — results are ordered best-match-first, each carries a 0–100 score plus differences and links, and defaults are year-round, abroad-only, 25,000+ people. It does not state result volume caps or failure behavior when a place name is ambiguous beyond 'most populous match wins'.

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 compact sentences with the core purpose front-loaded and the modifiers and defaults following. The phrasing is dense and slightly telegraphic but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, no-output-schema tool, the description covers purpose, return shape (score, differences, links), ordering, and all default behaviors an agent needs to call it correctly. Nothing material is left for the agent to guess.

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 every parameter is already documented, and the description largely restates those defaults (year-round, abroad-only, 25,000+) rather than adding new meaning. It does add the useful note that adjustments can be stacked freely except warmer with cooler, which goes slightly beyond the schema's own phrasing.

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 and relation: 'Towns whose climate is most like a town's, best match first', which clearly frames this as a similarity search rather than a lookup or pairwise comparison. It does not explicitly name siblings like compare_climates or get_climate, so the differentiation is implicit rather than stated.

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?

Gives useful context on optional modifiers ('but warmer / cooler / drier / sunnier / less humid'), single-month comparison, and geographic scoping, plus the app-consistent defaults. However, it never says when to prefer this over compare_climates or get_climate, leaving the alternative-selection decision to inference.

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