Skip to main content
Glama

get_station

Retrieve BirdWeather station metadata—name, location, coordinates, timezone, detection range, and thresholds—plus all-time REST stats when a station token is configured.

Instructions

Get station metadata: name, location, coords, timezone, detection range, thresholds.

If BIRDWEATHER_STATION_TOKEN is set, also includes all-time REST stats.

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_station"
  }
}

Input Schema

NameRequiredDescriptionDefault
station_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.5

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose one real conditional trait: all-time REST stats are included only when BIRDWEATHER_STATION_TOKEN is set. That is genuinely useful context, but it omits permission expectations, what happens for an unknown station_id, and the data volume/cost of the all-time stats path.

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?

Two tight sentences with the core purpose front-loaded and the conditional behavior clearly flagged as conditional. The phrase 'all-time REST stats' is slightly jargon-heavy and could be spelled out, but nothing is wasted.

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 shape need not be described, and the field list plus the token-conditional note covers the core. However, with no annotations and the closest helper being search_stations, the definition should have said how an agent obtains or validates a station_id to be fully self-sufficient.

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?

There is exactly one parameter and schema description coverage is 0%, so the schema adds nothing. The description never states the accepted station_id format (slug, numeric id, callsign) or where to obtain one, leaving the sole parameter underspecified beyond its self-evident name.

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?

States a specific verb and resource and enumerates the returned fields (name, location, coords, timezone, detection range, thresholds), which clearly separates it from count/trend siblings like station_counts or species_trend. It stops short of distinguishing itself from search_stations, which is the nearest ambiguous neighbor.

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 only implied: the tool takes a station_id, so an agent can infer it is for fetching details of an already-known station. There is no explicit guidance such as 'use search_stations to find a station_id first' or any statement about when not to use it.

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