Skip to main content
Glama
mattjegan

eBird MCP Server

by mattjegan

get_taxonomic_groups

Retrieve taxonomic bird groups like 'Waterfowl' or 'Raptors' from eBird data, supporting multiple classification systems and languages for birdwatching research and identification.

Instructions

Get species groups (e.g., 'Waterfowl', 'Raptors').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
species_groupingNo'ebird' for taxonomic order, 'merlin' for similar birds groupedebird
group_name_localeNoLanguage for group namesen

Implementation Reference

  • The handler function for the 'get_taxonomic_groups' tool. It makes an eBird API request to retrieve species groups based on the provided grouping and locale, then returns the result as formatted JSON text.
    async (args) => {
      const result = await makeRequest(`/ref/sppgroup/${args.species_grouping}`, {
        groupNameLocale: args.group_name_locale,
      });
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • The Zod input schema for the 'get_taxonomic_groups' tool, defining parameters 'species_grouping' (ebird or merlin) and 'group_name_locale'.
    {
      species_grouping: z.enum(["ebird", "merlin"]).default("ebird").describe("'ebird' for taxonomic order, 'merlin' for similar birds grouped"),
      group_name_locale: z.string().default("en").describe("Language for group names"),
    },
  • src/index.ts:512-525 (registration)
    The registration of the 'get_taxonomic_groups' tool using server.tool(), including name, description, schema, and handler.
    server.tool(
      "get_taxonomic_groups",
      "Get species groups (e.g., 'Waterfowl', 'Raptors').",
      {
        species_grouping: z.enum(["ebird", "merlin"]).default("ebird").describe("'ebird' for taxonomic order, 'merlin' for similar birds grouped"),
        group_name_locale: z.string().default("en").describe("Language for group names"),
      },
      async (args) => {
        const result = await makeRequest(`/ref/sppgroup/${args.species_grouping}`, {
          groupNameLocale: args.group_name_locale,
        });
        return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves species groups but does not mention whether this is a read-only operation, potential rate limits, authentication needs, or what the output format might be. This leaves significant gaps for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose with illustrative examples. It is front-loaded with the core action and avoids any unnecessary details, making it highly concise and well-structured.

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?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It explains what the tool does but lacks details on output format, error handling, or behavioral traits, which are important for completeness in the absence of annotations and output schema.

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?

The input schema has 100% description coverage, clearly documenting both parameters with enums and defaults. The description adds no additional parameter semantics beyond implying the tool returns grouped species data, which aligns with the schema. This meets the baseline score when schema coverage is high.

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 clearly states the tool's purpose as 'Get species groups' with examples like 'Waterfowl' and 'Raptors', which is specific and actionable. However, it does not explicitly differentiate from sibling tools like 'get_taxonomy' or 'get_taxonomic_forms', which might have overlapping functionality, so it falls short of a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'get_taxonomy' or 'get_species_list'. It lacks context about use cases, exclusions, or prerequisites, leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mattjegan/ebird-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server