Skip to main content
Glama
danmarce

weather-mcp

by danmarce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get forecast

get_forecast
Read-onlyIdempotent

Retrieve current conditions and a daily forecast for any location by place name or coordinates, returning structured weather data plus a ready-to-share card.

Instructions

Current conditions + an N-day daily forecast for a place. Returns the structured DATA in the text block (for you to answer from) and a weather card as card_markdown: include that markdown in your reply, unchanged, so the user sees the card.

    Args:
        location: a place name ("Quito", "Berlin, DE"); geocoded via Open-Meteo. Ignored if
            latitude+longitude are given. With neither, the server's default location is used.
        latitude/longitude: exact coordinates (both required together) — overrides `location`.
        days: number of daily-forecast days, 1..16 (default 3).
        units: "metric" (°C, km/h, mm — default) or "imperial" (°F, mph, in).
        language: language for geocoding the place name (default from config, e.g. "en"/"es").
        card: "auto" (default: an image link when this server can serve one, else a text card),
            "image" (image link; falls back to text when no link can be served), "text" (a monospace
            card in a ```text fence, for terminals or clients that don't show images) or "none".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardNoauto
daysNo
unitsNometric
languageNo
latitudeNo
locationNo
longitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it explains the dual return shape (structured DATA in the text block plus a `card_markdown` field) and instructs the agent to echo the markdown unchanged, which is non-obvious.

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 high-value information (what it returns, and the card_markdown instruction) is front-loaded before the Args block, and each parameter line earns its place. The Args list is somewhat dense but no line is redundant, so it stays efficient for a 7-parameter tool.

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?

With no output schema, the description compensates by describing the return payload and the card_markdown contract explicitly. Combined with the annotation-covered safety profile and the complete parameter documentation, an agent has everything needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so: it documents location vs latitude/longitude precedence, the 1..16 range and default for days, the exact unit systems for metric/imperial, the language parameter's purpose, and all four card modes with fallback behavior. This adds substantial meaning the bare schema lacks.

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 opening sentence states a specific verb and resource — 'Current conditions + an N-day daily forecast for a place' — with explicit scope (current + N-day). It is clearly distinguishable from the sibling geocode tool, which resolves names rather than returning weather.

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 description explains the precedence rules between location and latitude/longitude and notes the server-default fallback, which is real usage guidance. However, it never states when to use this tool versus the sibling geocode, nor when-not to use it, so an agent must infer the routing.

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

Deploy Server

Other Tools