Tanod MCP server

weatherpeek: get an hourly weather forecast for a place or coordinates

get_weather

Read-onlyIdempotent

Get hourly weather forecasts for any city or latitude/longitude point, with up to 48 hours of data. Use place names or coordinates; not for safety-critical decisions.

Instructions

weatherpeek: hourly weather forecast for a point or a city. For airport observations use get_metar. Input: either lat and lon together, or place alone, plus optional hours. place matches cities of 15,000+ people offline ("City" or "City, CC" with an ISO country code); no match is a 404 place_not_found (not charged). Upstream errors are a 5xx and are not charged. Typically 0.1-2 s. Price: USD 0.002. Free: 5 weather forecasts per IP per UTC day. Data: MET Norway and GeoNames, both CC BY 4.0; credit them when you show or republish it (see attribution). Forecasts are numerical weather model output and can be wrong: not for safety-critical decisions (aviation, marine, severe-weather warnings); use official services for those. Docs: https://tanod.dev/learn/weather-api-no-key.html

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude (-90..90); give lat and lon together, or place.
`lon`	No	Longitude (-180..180); give lat and lon together, or place.
`hours`	No	Hourly rows to return (1-48, default 24).
`place`	No	City name, optionally "City, CC" with an ISO country code (cities with 15,000+ people); give place alone, or lat and lon.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`hours`	No
`units`	No
`cached`	No
`hourly`	No
`location`	No
`updated_at`	No
`attribution`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds substantial context beyond them: price, free daily quota, typical latency, 404 vs 5xx charging behavior, data sources, attribution requirements, and a model-accuracy caveat.

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?

The description is front-loaded with purpose and the key get_metar alternative, and it avoids filler. It is dense with several clauses about pricing, quotas, errors, attribution, and safety caveats, all of which are relevant but make it longer than ideal.

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?

An output schema exists, so return values need not be explained. The description covers all necessary calling context: input combinations, matching rules, error and charging behavior, latency, price, free quota, data attribution, and safety limitations.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful place-matching semantics beyond the schema: offline matching only for cities of 15,000+ people, ISO country-code format, and a 404 place_not_found outcome when unmatched.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and forecast type: an hourly weather forecast for a point or city. It distinguishes itself from the sibling get_metar by naming it as the airport-observations alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance: either lat/lon together or place alone, optional hours, and an alternative (get_metar) for airport observations. It also states when not to use it for safety-critical decisions and directs users to official services.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server