Skip to main content
Glama
kshayk

AviBase MCP Server

by kshayk

get_bird_report

Retrieve detailed reports on bird species including related species, conservation status, and geographic distribution from the AviBase dataset.

Instructions

Get a detailed report for a specific bird species including related species and comprehensive information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scientific_nameYesScientific name of the bird species (e.g., "Aquila chrysaetos")

Implementation Reference

  • The handler function for 'get_bird_report' that takes scientific_name, fetches data from the bird API, and returns a comprehensive formatted Markdown report including taxonomy, conservation status, distribution, and related species.
      async handleGetBirdReport(args) {
        const { scientific_name } = args;
        const endpoint = `/bird/${encodeURIComponent(scientific_name)}`;
        const response = await this.makeAPIRequest(endpoint);
    
        const bird = response.data.bird;
        const related = response.data.relatedInFamily;
    
        return {
          content: [
            {
              type: 'text',
              text: `# Detailed Report: ${bird.Scientific_name}
    
    ## Basic Information
    - **Scientific Name:** ${bird.Scientific_name}
    - **Common Name:** ${bird.English_name_AviList || 'No common name available'}
    - **Alternative Names:** ${bird.English_name_Clements_v2024 || bird.English_name_BirdLife_v9 || 'None listed'}
    - **Taxonomic Authority:** ${bird.Authority || 'Unknown'}
    
    ## Taxonomic Classification
    - **Order:** ${bird.Order}
    - **Family:** ${bird.Family} (${bird.Family_English_name || 'Family name not available'})
    - **Taxonomic Rank:** ${bird.Taxon_rank}
    
    ## Conservation & Status
    - **IUCN Red List Category:** ${bird.IUCN_Red_List_Category || 'Not assessed'}
    - **Conservation Status:** ${response.data.conservationStatus}
    - **Extinction Status:** ${bird.Extinct_or_possibly_extinct || 'Not extinct'}
    
    ## Geographic Distribution
    ${bird.Range ? `**Range:** ${bird.Range}` : '**Range:** No range data available'}
    
    ## Additional Information
    - **Type Locality:** ${bird.Type_locality || 'Not specified'}
    - **Original Description:** ${bird.Title_of_original_description || 'Not available'}
    - **Bibliographic Details:** ${bird.Bibliographic_details || 'Not available'}
    
    ## External Resources
    ${response.data.hasUrls.birdLife ? `- **BirdLife DataZone:** Available` : ''}
    ${response.data.hasUrls.birdsOfTheWorld ? `- **Birds of the World:** Available` : ''}
    ${response.data.hasUrls.originalDescription ? `- **Original Description:** Available` : ''}
    - **Species Code:** ${bird.Species_code_Cornell_Lab || 'Not available'}
    - **AvibaseID:** ${bird.AvibaseID || 'Not available'}
    
    ## Related Species in ${bird.Family}
    ${related.length > 0 ? related.map((rel, i) => `${i + 1}. **${rel.Scientific_name}** - ${rel.English_name_AviList || 'No common name'}`).join('\n') : 'No related species data available'}`,
            },
          ],
        };
      }
  • Input schema definition for the 'get_bird_report' tool, requiring a 'scientific_name' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        scientific_name: {
          type: 'string',
          description: 'Scientific name of the bird species (e.g., "Aquila chrysaetos")',
        },
      },
      required: ['scientific_name'],
    },
  • mcp-server.js:217-230 (registration)
    Registration of the 'get_bird_report' tool in the ListTools response, including name, description, and input schema.
    {
      name: 'get_bird_report',
      description: 'Get a detailed report for a specific bird species including related species and comprehensive information.',
      inputSchema: {
        type: 'object',
        properties: {
          scientific_name: {
            type: 'string',
            description: 'Scientific name of the bird species (e.g., "Aquila chrysaetos")',
          },
        },
        required: ['scientific_name'],
      },
    },
  • mcp-server.js:312-313 (registration)
    Dispatch case in the CallToolRequest handler that routes 'get_bird_report' calls to the handleGetBirdReport method.
    case 'get_bird_report':
      return await this.handleGetBirdReport(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. While it mentions what the tool returns ('detailed report'), it doesn't describe important behavioral aspects like whether this is a read-only operation, potential rate limits, authentication requirements, error conditions, or response format. The description is insufficient 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.

Conciseness4/5

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

The description is a single, efficient sentence that clearly states the tool's purpose. It's appropriately sized for a simple lookup tool and front-loads the essential information without unnecessary elaboration.

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?

For a tool with no annotations and no output schema, the description is incomplete. It mentions returning a 'detailed report' but provides no information about what that report contains, its structure, or any behavioral constraints. Given the lack of structured metadata, the description should do more to help an agent understand what to expect from this tool.

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 schema description coverage is 100%, with the single parameter 'scientific_name' fully documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the schema (e.g., it doesn't clarify format requirements or provide examples). With high schema coverage, the baseline score of 3 is appropriate.

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 with a specific verb ('Get') and resource ('detailed report for a specific bird species'), and it specifies the content includes 'related species and comprehensive information'. However, it doesn't explicitly differentiate from sibling tools like 'get_bird_stats' or 'get_conservation_status' that might also provide bird information.

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. With multiple sibling tools like 'get_birds_by_region', 'get_bird_stats', and 'search_birds', there's no indication of when this detailed species report is preferred over other bird-related queries.

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