Skip to main content
Glama

station_counts

Retrieve detection and unique-species counts for a BirdWeather station across a chosen date range or recent days.

Instructions

Detection and unique-species counts for a station over a time window.

Time window (station-local calendar days; no period parameter):

  • days (default 7): last N days including today, or

  • from_date / to_date as YYYY-MM-DD in station-local time. Timezone defaults to the station's timezone.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
to_dateNo
timezoneNo
from_dateNo
station_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.5

TDQS

A3.6/5.0
Behavior3/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 disclose meaningful behavior: station-local calendar days, inclusion of today, a 7-day default, and timezone fallback to the station's timezone. It says nothing about required validity of station_id, error behavior for unknown stations, or result limits/pagination.

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 one-line purpose is front-loaded and the time-window rules are broken into scannable bullets with no wasted sentences. The parenthetical 'no `period` parameter' is slightly defensive framing but usefully forecloses a plausible wrong assumption.

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 trickiest part of the contract — date semantics and timezone handling — is fully specified. What is missing is minor: whether the two date modes can be combined with `days` and what happens for an invalid or unknown station_id.

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 coverage is 0%, so the description must compensate, and it does for four of five parameters: `days` (last N including today, default 7), `from_date`/`to_date` (YYYY-MM-DD, station-local), and `timezone` (defaults to station timezone). Only the required `station_id` goes unmentioned, though its meaning is self-evident from the purpose statement.

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 resource (a station) and a specific output (detection counts and unique-species counts) bounded by a time window, which is far more informative than the tool name alone. It does not, however, distinguish itself from siblings such as daily_counts or top_species, leaving the agent to infer the split.

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 description explains how to scope the window (relative days vs. absolute from_date/to_date) and that they are mutually alternative modes, which is genuine usage guidance. It gives no guidance on when to choose this tool over daily_counts, recent_detections, or top_species.

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