Skip to main content
Glama
kshayk

AviBase MCP Server

by kshayk

get_extinct_species

Retrieve extinct or possibly extinct bird species from the AviBase dataset to analyze conservation status and biodiversity loss.

Instructions

Get all extinct or possibly extinct bird species.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default: 100)

Implementation Reference

  • The handler function that implements the core logic for the 'get_extinct_species' tool. It makes an API request to fetch extinct bird species data and formats a markdown response with key details.
      async handleGetExtinctSpecies(args) {
        const { limit = 100 } = args;
        const endpoint = `/extinct?limit=${limit}`;
        const response = await this.makeAPIRequest(endpoint);
    
        return {
          content: [
            {
              type: 'text',
              text: `# Extinct and Possibly Extinct Species
    
    đź’€ **${response.pagination.totalItems}** extinct or possibly extinct bird species documented
    
    **Extinct species:**
    ${response.data.slice(0, 20).map((bird, i) => `${i + 1}. **${bird.Scientific_name}**
       - Common name: ${bird.English_name_AviList || 'No common name'}
       - Family: ${bird.Family}
       - Last known: ${bird.Extinct_or_possibly_extinct || 'Unknown'}
       - Authority: ${bird.Authority || 'Unknown'}`).join('\n\n')}
    
    ${response.pagination.hasNext ? `\n*Note: Showing first ${response.data.length} of ${response.pagination.totalItems} total extinct species.*` : ''}
    
    This represents a significant loss of avian biodiversity and highlights the importance of conservation efforts.`,
            },
          ],
        };
      }
  • The input schema definition for the 'get_extinct_species' tool, including the optional 'limit' parameter. This is part of the tools list registered with the MCP server.
      name: 'get_extinct_species',
      description: 'Get all extinct or possibly extinct bird species.',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Maximum number of results to return (default: 100)',
            default: 100,
          },
        },
        required: [],
      },
    },
  • mcp-server.js:303-304 (registration)
    The switch case in the MCP tool request handler that registers and dispatches calls to the 'get_extinct_species' handler method.
    case 'get_extinct_species':
      return await this.handleGetExtinctSpecies(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 states the tool retrieves data ('Get'), implying a read-only operation, but doesn't disclose any behavioral traits such as rate limits, authentication needs, pagination, or what the return format looks like (e.g., list structure, fields included). For a tool with zero annotation coverage, this is a significant gap in transparency.

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: 'Get all extinct or possibly extinct bird species.' It is front-loaded with the core purpose, has zero wasted words, and is appropriately sized for the tool's simplicity. Every part of the sentence earns its place by specifying the action, scope, and resource.

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?

Given the tool's low complexity (one optional parameter) and lack of annotations and output schema, the description is incomplete. It adequately states what the tool does but fails to provide necessary context such as the return format, error handling, or any behavioral constraints. For a tool with no structured data beyond the input schema, the description should do more to compensate for these gaps.

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, with the 'limit' parameter fully documented in the schema itself. The description adds no additional meaning beyond what the schema provides—it doesn't explain parameter interactions, default behavior beyond the schema's default, or semantic context. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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: 'Get all extinct or possibly extinct bird species.' It specifies the verb ('Get'), resource ('bird species'), and scope ('extinct or possibly extinct'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_conservation_status' or 'get_bird_report', which might also involve conservation status data.

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. It doesn't mention sibling tools like 'get_conservation_status' (which might provide broader conservation data) or 'search_birds' (which could filter for extinct species), nor does it specify prerequisites or exclusions. Usage is implied by the purpose but not explicitly defined.

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