Skip to main content
Glama
kshayk

AviBase MCP Server

by kshayk

get_birds_by_taxonomy

Retrieve bird species filtered by taxonomic classification such as Order, Family, or specific rank to identify and study related avian groups.

Instructions

Get birds filtered by taxonomic classification (Order, Family, or taxonomic rank).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelYesTaxonomic level to filter by
valueYesValue to filter by (e.g., "Strigiformes" for owls, "Accipitridae" for hawks)
limitNoMaximum number of results to return (default: 50)

Implementation Reference

  • The handler function that implements the tool logic: destructures args for level, value, limit; constructs API endpoint `/taxonomy/${level}/${value}`; fetches data using makeAPIRequest; computes species count; returns formatted markdown text with summary and sample records.
      async handleGetBirdsByTaxonomy(args) {
        const { level, value, limit = 50 } = args;
        const endpoint = `/taxonomy/${level}/${encodeURIComponent(value)}?limit=${limit}`;
        const response = await this.makeAPIRequest(endpoint);
    
        const speciesCount = response.data.filter(bird => bird.Taxon_rank === 'species').length;
        
        return {
          content: [
            {
              type: 'text',
              text: `# ${level}: ${value}
    
    📊 **Summary:**
    - **Total records:** ${response.pagination.totalItems}
    - **Species in results:** ${speciesCount}
    
    **Sample records:**
    ${response.data.slice(0, 10).map((bird, i) => `${i + 1}. **${bird.Scientific_name}** (${bird.Taxon_rank})
       - Common name: ${bird.English_name_AviList || 'No common name'}
       - Family: ${bird.Family}
       - Conservation: ${bird.IUCN_Red_List_Category || 'Not assessed'}`).join('\n\n')}
    
    ${response.pagination.hasNext ? `\n*Note: Showing first ${response.data.length} of ${response.pagination.totalItems} total records.*` : ''}`,
            },
          ],
        };
      }
  • mcp-server.js:104-127 (registration)
    Tool registration in ListToolsRequestSchema handler: defines name, description, and inputSchema specifying parameters level (enum: Order, Family, Taxon_rank), value (string), limit (number, default 50), required: level, value.
    {
      name: 'get_birds_by_taxonomy',
      description: 'Get birds filtered by taxonomic classification (Order, Family, or taxonomic rank).',
      inputSchema: {
        type: 'object',
        properties: {
          level: {
            type: 'string',
            description: 'Taxonomic level to filter by',
            enum: ['Order', 'Family', 'Taxon_rank'],
          },
          value: {
            type: 'string',
            description: 'Value to filter by (e.g., "Strigiformes" for owls, "Accipitridae" for hawks)',
          },
          limit: {
            type: 'number',
            description: 'Maximum number of results to return (default: 50)',
            default: 50,
          },
        },
        required: ['level', 'value'],
      },
    },
  • mcp-server.js:294-295 (registration)
    Dispatch case in CallToolRequestSchema switch statement that routes calls to the handleGetBirdsByTaxonomy handler.
    case 'get_birds_by_taxonomy':
      return await this.handleGetBirdsByTaxonomy(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions filtering but doesn't describe the return format (e.g., list of birds with details), pagination behavior, error handling, or any rate limits. For a query tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 front-loads the core purpose without unnecessary words. Every part of the sentence earns its place by specifying the action, resource, and filtering criteria, 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 no annotations and no output schema, the description is incomplete for a query tool with 3 parameters. It covers the basic purpose but lacks details on return values, error conditions, or behavioral traits. However, the high schema coverage partially compensates, making it minimally adequate but with clear gaps in context.

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 100%, so the schema already documents all parameters (level, value, limit) with descriptions and examples. The description adds no additional parameter semantics beyond what's in the schema, such as explaining the relationship between level and value or edge cases. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'birds' with specific filtering criteria 'by taxonomic classification', making the purpose evident. It distinguishes from siblings like 'get_birds_by_region' or 'get_birds_by_authority' by specifying the taxonomic focus, though it doesn't explicitly contrast with all alternatives.

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 siblings like 'search_birds' or 'custom_bird_query', nor does it mention prerequisites or exclusions. It implies usage for taxonomic filtering but lacks explicit context or alternatives, leaving the agent to infer based on tool names 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/kshayk/avibase-mcp'

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