Skip to main content
Glama

Best weather for the money

weather_for_the_money
Read-onlyIdempotent

Cities of 500,000+ ranked by how much nicer their weather is than their cost of living predicts (value), with a 0–100 nice-weather score and cost of living (US = 100). Quadrants: sweet (fine weather, affordable), pricey, tough (cheap, harder climate), other. Countries under a US 'do not travel' advisory are left out.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "weather_for_the_money"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax cities. Default 15
countryNoOnly this ISO country code
quadrantNoOnly one quadrant

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and closed-world behaviour, so the bar is lower; the description still adds real context by defining the scoring methodology, the quadrant taxonomy, and a non-obvious filtering rule (countries under a US 'do not travel' advisory are excluded). It leaves out result ordering beyond 'ranked', data vintage, and how ties or missing cost data are handled.

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?

Three short sentences, front-loaded with the ranking definition, followed by the quadrant legend and the exclusion rule. No filler; every clause carries information an agent would otherwise have to guess.

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 describing returns and does so adequately: ranked cities, a 0–100 nice-weather score, and a cost-of-living index. It is slightly thin on the remaining returned fields (city name, country) and on result-count defaults, which the schema covers for limit.

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, but the description genuinely adds meaning: it explains what each quadrant label means ('sweet' = fine weather and affordable, 'tough' = cheap but harder climate) and clarifies that cost of living is indexed with US = 100, which the schema does not state. The 'country' and 'limit' parameters are not further elaborated.

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 a precise verb+resource: cities of 500,000+ ranked by weather value relative to cost of living, with the derived metric ('how much nicer their weather is than their cost of living predicts') spelled out. It does not explicitly differentiate itself from siblings like best_weather_in_month or compare_climates, so it falls 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 implied by the framing (find affordable places with good weather), but there is no explicit when-to-use/when-not guidance and no named alternative for related questions such as month-specific weather or head-to-head comparison. The agent must infer routing from sibling names alone.

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