Skip to main content
Glama

get_weather

Read-onlyIdempotent

Get live weather forecast for a location from Vedurstofa.

Provide either operator_id OR latitude+longitude.
Returns temperature, wind, conditions for today and next 2-3 days.
Response includes `location` with name, latitude, longitude for map context.

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

Input Schema

NameRequiredDescriptionDefault
latitudeNoWGS84 latitude. Required if operator_id is not provided.
longitudeNoWGS84 longitude. Required if operator_id is not provided.
operator_idNoOperator slug to resolve location automatically. Use this OR latitude+longitude, not both.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description contributes beyond that by naming the upstream source and the forecast horizon (today plus 2-3 days), which tells the agent what freshness and range to expect.

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?

Four short sentences with the core action and the location-input constraint front-loaded. The final sentence about the returned `location` field is somewhat redundant given the output schema, but nothing else wastes space.

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 annotations covering the safety profile, a fully described schema and an output schema documenting the return shape, the description only needs the source, the input-mode rule and the forecast horizon – all of which it supplies. Nothing an agent needs to invoke it correctly is missing.

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 the either/or requirement and the WGS84 formats are already documented in the schema. The description restates the exclusivity rule and the fact that operator_id resolves the location, adding only marginal meaning beyond what structured fields provide.

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?

States a specific verb and resource ('Get live weather forecast') plus the data source (Vedurstofa), which cleanly separates it from topical siblings like get_air_quality or get_aurora_forecast. An agent knows exactly what this returns without opening the schema.

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 gives an input-mode rule ('Provide either operator_id OR latitude+longitude'), which is useful, but it never states when to choose this tool over an alternative or what happens when neither mode is supplied. Usage is implied by the topic rather than explicitly framed.

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