Skip to main content
Glama

first_of_year

Identify species at a BirdWeather station whose first detection of the year or season falls within the arrival window, using station ID, year, and date bounds.

Instructions

Species whose first detection of the year (or season) falls in the arrival window.

Season bounds use since / until as YYYY-MM-DD in station-local time (not from_date / to_date or period). Default season is Jan 1–today; the arrival window is the last 14 days of that season.

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

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

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It does disclose real behavior: season defaults, the 14-day arrival-window rule, and that bounds are interpreted in station-local time. It omits whether the call is read-only, how results are ordered, and what happens when since/until conflict with year.

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?

Three short sentences, front-loaded with what the tool returns, followed by date-format semantics and defaults. No filler, though the parenthetical naming warning could be folded more tightly into the parameter note.

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 no explanation, and the core temporal semantics are covered. Still, four of six parameters (year, limit, timezone, station_id) get no meaning anywhere, which is a notable gap for a tool with zero annotation and zero schema-description support.

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% across six parameters, so the description must compensate, and it does the most valuable part: it specifies that season bounds go through since/until as YYYY-MM-DD and explicitly warns against from_date/to_date/period. It leaves year, limit, timezone, and station_id undefined, and never clarifies how the timezone parameter interacts with 'station-local time'.

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 filter: species whose first detection of the year/season falls inside an arrival window. That is concrete enough to distinguish it from a generic listing, but it never names or contrasts with the obvious siblings (new_arrivals, recent_detections, species_trend), so the agent must infer the boundary.

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?

Usage context is only implied through the default behavior (Jan 1–today season, last 14 days as the arrival window). There is no explicit statement of when this tool is preferred over alternatives such as new_arrivals or recent_detections, and no exclusions or prerequisites are given.

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