Skip to main content
Glama

species_trend

Count detections of a single species over time at a BirdWeather station, with daily or weekly granularity and an optional date range.

Instructions

Counts over time for one species at a station (station-local days or weeks).

Time window (station-local; no period parameter): days (default 30) or from_date / to_date as YYYY-MM-DD. Granularity is day or week.

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>",
      "species": "<species>"
    },
    "name": "species_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
speciesYes
to_dateNo
timezoneNo
from_dateNo
station_idYes
granularityNoday

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, the description must carry the behavioral load; it does disclose that time windows are station-local, that the default window is 30 days, and that granularity is day or week. It does not state what happens if `days` and `from_date`/`to_date` are both supplied, whether results are capped or paginated, or any auth/rate considerations.

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, front-loaded statements with no filler; the scope and the time-window semantics come first. Minor noise from inconsistent backtick formatting (``day``) and a parenthetical that partially repeats the following line.

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 described. For a 7-parameter tool with zero schema descriptions and no annotations, however, key operational gaps remain: the precedence rule between `days` and `from_date`/`to_date`, and the role of `timezone` against station-local time.

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?

Schema coverage is 0% across 7 parameters, so the description has to compensate and only partly does: it documents `days` default, the YYYY-MM-DD format for the date pair, and the day/week granularity. `timezone`, `species`, and `station_id` go entirely unexplained, and the timezone parameter's relationship to the stated 'station-local' semantics is left ambiguous.

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 — 'Counts over time for one species at a station' — which distinguishes it from aggregate siblings like station_counts or top_species. The parenthetical scoping of 'station-local days or weeks' sharpens the unit of analysis, though it does not explicitly name an alternative tool.

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 implies the use case (trend over time for a single species at a single station) but offers no explicit when-to-use/when-not or routing to siblings such as daily_counts or compare_stations. The only guidance given is internal to the call (days vs from_date/to_date), not about tool selection.

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