Skip to main content
Glama

get_weather

Fetch current weather conditions for a BirdWeather station by station ID when a reading is available.

Instructions

Current weather reading for a station, when BirdWeather has one.

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": {
      "station_id": "<station_id>"
    },
    "name": "get_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
station_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.5

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden, and it does add one genuinely useful behavioral fact: the reading may not exist for a given station, so callers must handle absence. It says nothing about data freshness, failure modes, or whether a station with no sensor returns null versus an error, which leaves meaningful gaps for a tool with zero annotation coverage.

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?

One short, front-loaded sentence with no wasted wording, and the resource and subject are stated first. Its brevity borders on under-specification rather than true economy, which keeps it below a 5.

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

Completeness3/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 described, and the tool has only one parameter, which lowers the completeness bar considerably. Still, for a definition with no annotations the description omits freshness, the missing-data behavior beyond a hint, and how to source a station ID, leaving it merely adequate.

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 description coverage is 0%, so the description must compensate, and it only partially does: 'for a station' confirms that station_id identifies the station, but gives no format, no hint about where to obtain a valid ID (e.g., search_stations). With a single trivially named parameter the impact is limited, but the meaning added beyond the schema is minimal.

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 gives a specific verb and resource ('Current weather reading for a station'), so an agent can immediately tell this returns weather rather than detections, counts, or species data like the sibling tools. It stops short of naming any sibling or explicitly contrasting scopes, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus alternatives, no stated prerequisites, and no note about which station identifiers are valid. The only usage-adjacent phrase, 'when BirdWeather has one,' is a vague availability qualifier rather than a selection rule.

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