Skip to main content
Glama
mattjegan

eBird MCP Server

by mattjegan

get_taxonomy_versions

Retrieve available taxonomy versions from the eBird API to ensure accurate bird species identification and data consistency.

Instructions

Get all available taxonomy versions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the get_taxonomy_versions tool. It makes an API request to fetch taxonomy versions and returns the result as JSON-formatted text content.
    async () => {
      const result = await makeRequest("/ref/taxonomy/versions");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • Empty Zod schema indicating the tool takes no input parameters.
    {},
  • src/index.ts:502-510 (registration)
    Registration of the get_taxonomy_versions tool using McpServer.tool() with description, schema, and inline handler.
    server.tool(
      "get_taxonomy_versions",
      "Get all available taxonomy versions.",
      {},
      async () => {
        const result = await makeRequest("/ref/taxonomy/versions");
        return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
      }
    );
  • Shared helper function used by the handler to make authenticated HTTP requests to the eBird API.
    async function makeRequest(endpoint: string, params: Record<string, string | number | boolean> = {}): Promise<unknown> {
      const url = new URL(`${BASE_URL}${endpoint}`);
      Object.entries(params).forEach(([key, value]) => {
        if (value !== undefined && value !== null) {
          url.searchParams.append(key, String(value));
        }
      });
    
      const response = await fetch(url.toString(), {
        headers: { "X-eBirdApiToken": API_KEY! },
      });
    
      if (!response.ok) {
        throw new Error(`eBird API error: ${response.status} ${response.statusText}`);
      }
    
      return response.json();
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without behavioral details. It doesn't mention if this is a read-only operation, how data is returned (e.g., list format, pagination), or any constraints like rate limits or authentication needs.

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, clear sentence with no wasted words. It's front-loaded and efficiently communicates the core purpose without unnecessary elaboration.

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 has 0 parameters and no output schema, the description is minimally adequate but lacks details on return values or behavioral context. It's complete enough for a simple retrieval tool but could benefit from more context about what 'taxonomy versions' entails.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description appropriately doesn't mention parameters, aligning with the schema. A baseline of 4 is given as it doesn't need to compensate for any gaps.

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 verb ('Get') and resource ('all available taxonomy versions'), making the purpose understandable. It doesn't explicitly differentiate from sibling tools like 'get_taxonomy' or 'get_taxonomic_groups', but the specificity of 'versions' provides some implicit distinction.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_taxonomy' or other taxonomy-related siblings. The description only states what it does, not when it's appropriate or what context it serves.

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