Skip to main content
Glama

compare_stations

Compare species lists between two BirdWeather stations over the same time window to identify shared and unique species.

Instructions

Compare species lists for two stations over the same window (overlap and uniques).

Time window (station-local; no period parameter): days (default 7) or from_date / to_date as YYYY-MM-DD.

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_a": "<station_a>",
      "station_b": "<station_b>"
    },
    "name": "compare_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
to_dateNo
timezoneNo
from_dateNo
station_aYes
station_bYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.5

TDQS

B3.1/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 burden and does disclose useful behavior: the window is station-local and there is deliberately no `period` parameter, plus the default of 7 days and date format. It stays silent on whether the operation is read-only, what happens with an unknown station, how `limit` affects the comparison, and how timezone interacts with the window.

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 short blocks, intentionally front-loaded: outcome first, time-window rules second. The `period` aside is slightly defensive but earns its place by preempting a wrong parameter.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with zero schema descriptions and no annotations, the description leaves key gaps: station identifier format, `limit` behavior, `timezone` effect, days-vs-date-range precedence, and error behavior. The output schema covers the return shape, but the invocation side is under-described.

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 coverage is 0% across 7 parameters, so the description must compensate; it only does so for `days`, `from_date`, `to_date` (format and default). It says nothing about `station_a`/`station_b` identifier format (ID vs name), `limit`, or `timezone`, and it doesn't state whether `days` is ignored when a date range is given - a precedence question an agent will actually hit.

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?

Names a specific action and resource ('Compare species lists for two stations') and adds the result shape ('overlap and uniques'), which tells an agent what it gets back. It doesn't explicitly differentiate itself from the nearest-looking sibling (station_counts), but the verb+resource is unambiguous enough to route correctly.

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 implied: pick two stations and one shared time window. There is no explicit when-to-use versus alternatives (e.g. search_stations or species_list) and no stated exclusions or prerequisites, so an agent must infer the choice.

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