Skip to main content
Glama

top_species

Retrieve and rank bird species by detection count for a BirdWeather station within a chosen time window, using either a day range or start/end dates.

Instructions

Top species by detection count for a station (alias: species_list).

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_id": "<station_id>"
    },
    "name": "top_species"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
offsetNo
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

B3.2/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; it does disclose that time filtering is station-local and that defaults are 7 days, which is real behavioral context. It omits pagination behavior (limit/offset), ordering details beyond 'by detection count', and any permission or failure characteristics.

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 paragraphs with the core purpose front-loaded and the time-window rule cleanly separated. No filler, though the alias parenthetical is slightly awkwardly placed.

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 needn't be explained, but for a 7-parameter tool with zero schema coverage and no annotations, the description leaves pagination and timezone semantics ambiguous. Adequate for the happy path, thin for full correct invocation.

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%, so the description must explain all 7 parameters, but it only covers days, from_date, to_date, and implicitly timezone via 'station-local'. limit, offset, station_id, and the timezone field itself are left entirely undocumented.

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 resource and metric: 'Top species by detection count for a station.' The alias note ('alias: species_list') reveals a duplicate entry point, which is useful, but the description never distinguishes it from siblings like search_species or species_trend.

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?

Gives clear guidance on the time-window mechanism (days default 7, or from_date/to_date as YYYY-MM-DD) and explicitly rules out a `period` parameter. However, it offers no guidance on when to reach for this tool versus species_list, search_species, or species_trend.

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