Skip to main content
Glama

new_arrivals

Retrieve newly detected bird species at a BirdWeather station within a specified arrival window to track first-of-year appearances.

Instructions

Alias for first_of_year: new species arrivals in the recent arrival window.

Season bounds use since / until as YYYY-MM-DD (not from_date / to_date or period).

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

Input Schema

NameRequiredDescriptionDefault
yearNo
limitNo
sinceNo
untilNo
timezoneNo
station_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.5

TDQS

B3.1/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 it does disclose two non-obvious traits: the tool is an alias of first_of_year and its season-bound parameter names differ from the convention used elsewhere (from_date/to_date/period). It says nothing about permissions, rate limits, defaults such as limit=50 or timezone, or how the default arrival window interacts with since/until.

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 sentences, front-loaded with the identity/alias relationship and followed by the parameter-naming caveat. Nothing is padded, though the parenthetical about invalid parameter names is slightly awkward.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter tool with no annotations, the description leaves critical gaps: what the 'recent arrival window' means, whether since/until override it, and what year, limit, and timezone do. The output schema covers return values, but invocation semantics are under-specified.

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% across six parameters, so the description must compensate. It only addresses since/until (including the YYYY-MM-DD format and the negative guidance that from_date/to_date/period are invalid) and leaves year, limit, timezone, and station_id entirely unexplained, so most parameters remain 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?

The description names the resource concretely (new species arrivals) and explicitly ties it to the sibling first_of_year as an alias, so an agent can map it to the right concept without opening the schema. It stops short of a crisp verb and leaves 'recent arrival window' undefined, which keeps it from a 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 'alias for first_of_year' framing implies the tool is interchangeable with that sibling, which is weak but real routing guidance. There is no explicit when-to-use vs when-not statement, no prerequisites, and no guidance on when the alias should be preferred over the canonical tool.

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