Skip to main content
Glama

activity_by_hour

Build an hourly bird detection histogram for a station in local time, optionally filtered by species and date range, to reveal daily activity patterns.

Instructions

Hourly detection histogram in station-local time (optional species filter).

Time window (station-local; no period parameter): days (default 7) or from_date / to_date as YYYY-MM-DD. There is no hours argument — the result always covers hours 0–23.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
speciesNo
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.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: results are station-local, the histogram always spans hours 0–23, and there is deliberately no `hours` argument or `period` parameter. It does not state permissions, cost, or that the operation is read-only, but the coverage of result shape is above average for an unannotated tool.

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?

Front-loaded with the result shape, then the time-window rules. The negative-space notes ('no `period` parameter', 'no `hours` argument') are slightly unusual but earn their place by heading off the most likely parameter mistakes. No filler prose.

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 not be explained, and the time window is well covered. However, gaps remain for a 6-parameter tool: `timezone` semantics vs the stated station-local behavior, and what `station_id` must reference, are left for the agent to guess.

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 6 parameters, so the description must compensate. It documents `days` (default 7), the date format for `from_date`/`to_date`, and the optional `species` filter, but leaves `station_id` and especially `timezone` unexplained — the latter is notable because the description asserts 'station-local time' while the schema exposes a `timezone` override, and how they interact is unstated.

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 shape: an 'hourly detection histogram in station-local time (optional species filter)'. That distinguishes it from aggregate siblings like daily_counts or top_species by granularity, though it never names an alternative explicitly.

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?

It gives real guidance on the time-window choice — use `days` (default 7) or `from_date`/`to_date` in YYYY-MM-DD — but that is parameter guidance, not tool-selection guidance. There is no statement of when to prefer this over daily_counts or recent_detections.

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