Skip to main content
Glama
kshayk

AviBase MCP Server

by kshayk

get_birds_by_authority

Retrieve bird species described by a specific taxonomic authority like Linnaeus or Darwin from the AviBase dataset.

Instructions

Find birds described by a specific taxonomic authority (e.g., Linnaeus, Darwin, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authorityYesName of the taxonomic authority
limitNoMaximum number of results to return (default: 50)

Implementation Reference

  • The main handler function that implements the get_birds_by_authority tool. It extracts authority and limit from args, calls the /authority API endpoint, and returns a formatted markdown response with bird details.
      async handleGetBirdsByAuthority(args) {
        const { authority, limit = 50 } = args;
        const endpoint = `/authority?name=${encodeURIComponent(authority)}&limit=${limit}`;
        const response = await this.makeAPIRequest(endpoint);
    
        return {
          content: [
            {
              type: 'text',
              text: `# Birds Described by ${authority}
    
    👨‍🔬 **${response.pagination.totalItems}** birds described by ${authority}
    
    **Historical contributions:**
    ${response.data.slice(0, 15).map((bird, i) => `${i + 1}. **${bird.Scientific_name}**
       - Common name: ${bird.English_name_AviList || 'No common name'}
       - Family: ${bird.Family}
       - Year: ${bird.Authority}
       - Publication: ${bird.Bibliographic_details ? bird.Bibliographic_details.substring(0, 80) + '...' : 'Not specified'}`).join('\n\n')}
    
    ${response.pagination.hasNext ? `\n*Note: Showing first ${response.data.length} of ${response.pagination.totalItems} total species described by ${authority}.*` : ''}`,
            },
          ],
        };
      }
  • Input schema for the get_birds_by_authority tool, defining required 'authority' string parameter and optional 'limit' number.
    inputSchema: {
      type: 'object',
      properties: {
        authority: {
          type: 'string',
          description: 'Name of the taxonomic authority',
        },
        limit: {
          type: 'number',
          description: 'Maximum number of results to return (default: 50)',
          default: 50,
        },
      },
      required: ['authority'],
    },
  • mcp-server.js:182-200 (registration)
    Tool registration in the listTools response, including name, description, and input schema.
    {
      name: 'get_birds_by_authority',
      description: 'Find birds described by a specific taxonomic authority (e.g., Linnaeus, Darwin, etc.).',
      inputSchema: {
        type: 'object',
        properties: {
          authority: {
            type: 'string',
            description: 'Name of the taxonomic authority',
          },
          limit: {
            type: 'number',
            description: 'Maximum number of results to return (default: 50)',
            default: 50,
          },
        },
        required: ['authority'],
      },
    },
  • mcp-server.js:306-307 (registration)
    Dispatch case in the CallToolRequestSchema handler that routes calls to get_birds_by_authority to its handler function.
    case 'get_birds_by_authority':
      return await this.handleGetBirdsByAuthority(args);
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description mentions what the tool does but doesn't disclose any behavioral traits such as whether it's read-only, potential rate limits, authentication requirements, error conditions, or what the output looks like (e.g., list format, pagination). For a query tool with no annotation coverage, this leaves significant gaps in understanding how it 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 ('Find birds described by a specific taxonomic authority') and includes helpful examples in parentheses. There's no wasted verbiage, repetition, or unnecessary elaboration, making it easy to parse quickly.

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 complexity (a query with filtering), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like safety, performance, or output format, which are crucial for an AI agent to use it correctly. While the purpose is clear, the absence of annotations and output details means the description should do more to compensate, which it doesn't.

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%, with both parameters (authority, limit) well-documented in the schema. The description adds minimal value beyond the schema by providing examples of authorities (Linnaeus, Darwin), which slightly clarifies the expected format. However, it doesn't explain parameter interactions, constraints, or usage nuances, so it meets the baseline for high schema coverage without significant enhancement.

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 'Find' and resource 'birds' with specific filtering criteria 'described by a specific taxonomic authority', making the purpose immediately understandable. It provides examples (Linnaeus, Darwin) to clarify the authority parameter. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_birds_by_taxonomy' or 'search_birds', which might also involve taxonomic filtering.

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 involving bird queries (custom_bird_query, get_birds_by_region, get_birds_by_taxonomy, search_birds), there's no indication of when this authority-based filtering is preferred over other filtering methods or what makes it unique in the toolset.

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