Skip to main content
Glama

recent_detections

Retrieve recent bird detections for a specific BirdWeather station, filtered by species, confidence, and date range, with pagination for browsing results.

Instructions

List recent detections for a station.

Filters: optional species (id, common name, or scientific name), min_confidence (0–1). Time window (station-local; no period parameter): days (default 1) or from_date / to_date as YYYY-MM-DD. Use after with the previous page_info.endCursor for pagination. When BIRDWEATHER_STATION_TOKEN is set, the station REST API is preferred (extra fields like image URLs).

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

Input Schema

NameRequiredDescriptionDefault
daysNo
afterNo
limitNo
speciesNo
to_dateNo
timezoneNo
from_dateNo
station_idYes
min_confidenceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the time window is station-local, that the default is one day, how pagination works via page_info.endCursor, and that setting BIRDWEATHER_STATION_TOKEN switches to the preferred station REST API returning extra fields like image URLs. This is meaningful backend-switching context an agent cannot get elsewhere. Rate limits and auth failure behavior are still unmentioned, keeping it from a 5.

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?

The purpose sentence leads, followed by filters, then the time window, pagination, and the token-dependent backend note in a logical order. Every sentence carries information; the only mild density cost is packing the time-window alternatives into one line.

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

Completeness4/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 explained, and the description covers the tricky semantics of time windowing, pagination, and backend selection for a 9-parameter tool. The remaining gap is the undocumented `limit` and `timezone` parameters against 0% schema coverage, which keeps it below a 5.

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

Parameters4/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 largely does: species accepts id, common name, or scientific name; min_confidence is bounded 0–1; days defaults to 1; from_date/to_date are YYYY-MM-DD; after takes the previous page_info.endCursor. Only `limit` and `timezone` are left undefined in both schema and description.

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 states a specific verb and resource ('List recent detections for a station'), making the operation immediately clear. 'Recent' is initially vague but is quickly pinned down by the default `days`=1 window. It stops short of differentiating against close siblings such as new_arrivals or daily_counts, so it lands at 4 rather than 5.

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 text explains how to drive the filters and time window, and the parenthetical 'no `period` parameter' implicitly warns the agent off a common wrong assumption. However, it never states when to choose this tool over alternatives like new_arrivals or station_counts, so the when-to-use guidance is only implied.

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