Skip to main content
Glama

daily_counts

Retrieve per-day bird detection totals for a BirdWeather station, with optional species breakdown and date-range or recent-day filtering.

Instructions

Per-day detection totals (and optional per-species breakdown) for a station.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
speciesNo
to_dateNo
timezoneNo
from_dateNo
station_idYes
include_species_breakdownNo

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; it does disclose that the window is station-local and that there is no `period` parameter, which prevents a wrong argument. It omits read-only confirmation, any rate/size limits, and precedence when both `days` and dates are supplied.

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 sentences with no wasted wording; the time-window rule is stated compactly. The note about a missing `period` parameter is slightly oblique but still relevant.

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 time-window logic is covered. Gaps remain for a 7-parameter tool: timezone meaning, species filter behavior, and argument precedence between `days` and the date range.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/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 must compensate and largely does not. It explains `days`, `from_date`/`to_date` formats, and gestures at the species breakdown, but leaves `timezone`, `species` filtering semantics, and the `days` vs. date-range interaction undefined.

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 scope: per-day detection totals for a station, with an optional per-species breakdown. An agent can distinguish it from siblings like activity_by_hour or species_trend, though no sibling is named directly.

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 mechanics for choosing a time window (days default 7, or from_date/to_date) and notes the absence of a `period` parameter, implying a sibling pattern. It never states when to prefer this tool over station_counts, species_trend, or recent_detections, so usage is implied rather than explicit.

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