Skip to main content
Glama

species_info

Look up bird species profiles by ID, scientific name, or free-text query to retrieve names, eBird/Wikipedia links, images, and summaries.

Instructions

Species profile: names, eBird/Wikipedia links, images, summary.

Look up by species_id, scientific_name, or a free-text query (common or scientific name).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "species_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
species_idNo
scientific_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.5

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It implies a passive read, but says nothing about permissions, whether a missing species errors or returns empty, or how the three optional keys interact when several or none are supplied — a real gap given that all parameters are optional.

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 sentences, front-loaded with the payload then the lookup keys, no filler. The payload enumeration is mildly redundant with the existing output schema, which keeps it from a 5.

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?

Having an output schema means return values needn't be explained, and the description covers inputs at a basic level. However, for a tool with zero required parameters and no annotations, the missing guidance on empty invocation and on multi-key resolution leaves a meaningful hole.

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% and the raw schema only exposes bare titles, so the description must compensate. It does name all three parameters and clarifies that the free-text query accepts common or scientific names, but it never states precedence between query/species_id/scientific_name or what happens when none is provided.

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 (species profile) and enumerates what it returns (names, eBird/Wikipedia links, images, summary), plus the lookup keys. An agent can tell this is a single-entity lookup rather than a list or search, though no sibling is named to make the boundary with search_species explicit.

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 second sentence gives the three ways to invoke it, which implies usage, but there is no statement of when to prefer this over search_species or species_list, and no exclusion or fallback guidance. Adequate context, no routing logic.

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