Skip to main content
Glama

search_species

Find BirdWeather species by common or scientific name fragment, returning matching catalog entries with optional pagination controls.

Instructions

Search BirdWeather's species catalog by common or scientific name fragment.

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": {
      "query": "<query>"
    },
    "name": "search_species"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.5

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and largely drops it. It says nothing about case sensitivity, partial/fuzzy matching scope, result ordering, empty-result behavior, or pagination, all of which matter for a search endpoint.

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?

A single front-loaded sentence with no filler or redundancy. It is tight, though the tightness reflects under-specification rather than disciplined editing.

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?

The presence of an output schema excuses it from describing return values, but for a 3-parameter search tool with zero schema coverage and no annotations, key operational details are missing: cursor-based pagination, default result size, and matching behavior. An agent can form a call but not predict its results.

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%, so the description needed to compensate and did not. Only 'query' is implicitly explained by 'name fragment'; the 'after' cursor and 'limit' (default 20) parameters are entirely undocumented as to their role, format, or pagination semantics.

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 gives a specific verb (search), a specific resource (BirdWeather's species catalog), and the matching rule (common or scientific name fragment). That is enough for an agent to tell it apart from species_info or species_list without opening the schema, though no sibling is named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance. The phrase 'name fragment' hints that a partial name is required, but the description never says when to prefer this over species_list or species_info, nor what happens with an empty or ambiguous query.

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