Skip to main content
Glama

species_list

Retrieve species heard at a BirdWeather station, ranked by detection count over a default 7-day window or custom date range.

Instructions

Alias for top_species: species heard at a station, ranked by count.

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

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

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description must explain behavior on its own. It correctly discloses that the time window is station-local, defaults to 7 days, and has no `period` parameter, but it never mentions pagination (despite limit and offset parameters), the read-only nature, or how the timezone override interacts with station-local time.

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?

Only two short sentences, with the alias and ranking semantics front-loaded before the time-window detail. The parenthetical about the missing `period` parameter devotes space to a negative that may not be actionable, but that is the only minor redundancy.

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?

The output schema is present, so the description does not need to explain return values, and its focus on the time-window logic is appropriate. It is still missing the pagination parameter meaning and the timezone override semantics; both are needed before this tool can be called with confidence.

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 description coverage is 0% across 7 parameters, so the description has to supply missing meaning. It usefully documents `days` (default 7), `from_date`/`to_date` (format YYYY-MM-DD), and the absence of `period`, but it leaves `limit`, `offset`, and `timezone` entirely undefined, and it is unclear whether from/to dates override `days`.

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 names a specific resource and operation: species heard at a station ranked by count. It also says the tool is an alias for top_species, which tells an agent how this tool differs from that sibling. The only weakness is that it never explains what an 'alias' means for outputs or defaults.

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?

Stating that the tool is an 'alias for top_species' implies the agent may call either and that duplication is expected. However, the description does not explain when to prefer this tool over search_species, recent_detections, or top_species itself, so usage guidance must be inferred.

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