Skip to main content
Glama
kshayk

AviBase MCP Server

by kshayk

get_conservation_status

Retrieve bird species by IUCN Red List conservation status categories such as Critically Endangered, Endangered, or Vulnerable to support biodiversity research and conservation planning.

Instructions

Get birds by IUCN Red List conservation status (CR=Critically Endangered, EN=Endangered, VU=Vulnerable, EX=Extinct, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesIUCN Red List category
limitNoMaximum number of results to return (default: 50)

Implementation Reference

  • The main handler function that implements the core logic for the 'get_conservation_status' tool. It makes an API request to fetch birds by IUCN category, maps category codes to full names, and formats a markdown response listing species with common names, families, and range info.
      async handleGetConservationStatus(args) {
        const { category, limit = 50 } = args;
        const endpoint = `/conservation/${category}?limit=${limit}`;
        const response = await this.makeAPIRequest(endpoint);
    
        const categoryNames = {
          'CR': 'Critically Endangered',
          'EN': 'Endangered', 
          'VU': 'Vulnerable',
          'NT': 'Near Threatened',
          'LC': 'Least Concern',
          'DD': 'Data Deficient',
          'EX': 'Extinct',
          'EW': 'Extinct in the Wild'
        };
    
        return {
          content: [
            {
              type: 'text',
              text: `# ${categoryNames[category] || category} Species
    
    🚨 **${response.pagination.totalItems}** species with IUCN status: **${category}**
    
    **Species list:**
    ${response.data.map((bird, i) => `${i + 1}. **${bird.Scientific_name}**
       - Common name: ${bird.English_name_AviList || 'No common name'}
       - Family: ${bird.Family}
       - Range: ${bird.Range ? bird.Range.substring(0, 100) + '...' : 'No range data'}`).join('\n\n')}
    
    ${response.pagination.hasNext ? `\n*Note: Showing first ${response.data.length} of ${response.pagination.totalItems} total species.*` : ''}`,
            },
          ],
        };
      }
  • Input schema for the tool defining the required 'category' parameter (IUCN enum) and optional 'limit' for result count.
    inputSchema: {
      type: 'object',
      properties: {
        category: {
          type: 'string',
          description: 'IUCN Red List category',
          enum: ['CR', 'EN', 'VU', 'NT', 'LC', 'DD', 'EX', 'EW'],
        },
        limit: {
          type: 'number',
          description: 'Maximum number of results to return (default: 50)',
          default: 50,
        },
      },
      required: ['category'],
    },
  • mcp-server.js:128-147 (registration)
    Tool registration entry returned by ListToolsRequestHandler, including name, description, and input schema.
    {
      name: 'get_conservation_status',
      description: 'Get birds by IUCN Red List conservation status (CR=Critically Endangered, EN=Endangered, VU=Vulnerable, EX=Extinct, etc.).',
      inputSchema: {
        type: 'object',
        properties: {
          category: {
            type: 'string',
            description: 'IUCN Red List category',
            enum: ['CR', 'EN', 'VU', 'NT', 'LC', 'DD', 'EX', 'EW'],
          },
          limit: {
            type: 'number',
            description: 'Maximum number of results to return (default: 50)',
            default: 50,
          },
        },
        required: ['category'],
      },
    },
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. It mentions the tool 'gets' birds (implying a read operation) but doesn't disclose behavioral traits like whether it requires authentication, rate limits, pagination behavior, or what the return format looks like (e.g., list of bird names, detailed records). For a tool with no annotations, 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 and includes helpful parenthetical explanations of category codes. Every word earns its place with no redundancy or unnecessary details, making it easy to parse quickly.

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 tool that returns data. It covers the purpose and parameters well but lacks information on what the output contains (e.g., bird names, full records, error handling) and behavioral aspects like rate limits. For a read operation with two parameters, this leaves the agent without full context on how to interpret results.

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 fully documents both parameters (category with enum values and limit with default). The description adds minimal value beyond the schema by listing some category examples (CR, EN, VU, EX, etc.), but doesn't explain parameter interactions or provide additional context like what 'etc.' includes. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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'), specifies the filtering criterion ('by IUCN Red List conservation status'), and distinguishes from siblings by focusing on conservation status rather than taxonomy, region, or other attributes. It provides specific category codes (CR, EN, VU, etc.) that help differentiate it from tools like get_extinct_species or get_birds_by_region.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool (when querying birds by conservation status) but doesn't explicitly state when not to use it or name alternatives. For example, it doesn't clarify that get_extinct_species might be a more specific alternative for extinct birds, or when to use search_birds for broader queries. The context is clear but lacks explicit exclusions or comparisons.

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