Skip to main content
Glama

search_stations

Find BirdWeather stations near a latitude/longitude within a chosen radius or by name; results include distance and are sorted nearest-first for nearby monitoring.

Instructions

Find stations near a lat/lon (default 25 km radius) and/or by name query.

Geographic results include distance_km from the search point, sorted nearest-first.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
afterNo
limitNo
queryNo
radius_kmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.5

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses the default search radius, the presence of distance_km in geographic results, and nearest-first ordering — real behavior beyond structured fields. But it omits whether an empty parameter set returns everything or errors, and says nothing about pagination despite an 'after' parameter, which matters for an unannotated read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, the primary capability is front-loaded, and the second sentence delivers the most decision-relevant output detail (distance + sort order). No filler or redundancy.

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 spelled out, and the description does note the geographic ordering. Still, for a 6-parameter unannotated tool, the unspecified default behavior with no filters and the undocumented pagination parameters leave meaningful gaps an agent would hit in practice.

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

Parameters2/5

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

Schema description coverage is 0% across 6 parameters, so the description must compensate. It adds meaning for lat, lon, query, and radius_km (including the 25 km default), but 'after' and 'limit' (default 20) are never mentioned, leaving pagination semantics entirely opaque.

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 — 'Find stations' — and enumerates the two selection modes: proximity to a lat/lon and name query, which can be combined ('and/or'). This distinguishes it from siblings like get_station (lookup) or compare_stations, though it never names an alternative explicitly.

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?

Implies usage through the 'and/or' phrasing: pass coordinates, a name query, or both. It also documents the default 25 km radius, which helps an agent decide whether to override radius_km. However, there is no explicit when-not guidance, no statement about what happens if all filters are omitted, and no routing to get_station or compare_stations.

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