Skip to main content
Glama
Augmented-Nature

Ensembl MCP Server

list_species

Retrieve available species and genome assemblies from Ensembl's genomic database to identify organisms for biological research and data analysis.

Instructions

Get list of available species and assemblies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
divisionNoEnsembl division (e.g., vertebrates, plants, fungi)

Implementation Reference

  • The handler function that implements the list_species tool. It makes a GET request to the Ensembl REST API '/info/species' endpoint, optionally filtering by division, and returns the JSON response containing available species and assemblies.
    private async handleListSpecies(args: any) {
      try {
        const params: any = {};
    
        if (args.division) {
          params.division = args.division;
        }
    
        const response = await this.apiClient.get('/info/species', { params });
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        return this.handleError(error, 'listing species');
      }
    }
  • src/index.ts:869-870 (registration)
    Registration of the list_species tool handler in the CallToolRequestSchema switch statement.
    case 'list_species':
      return this.handleListSpecies(args);
  • Tool schema definition including name, description, and input schema (optional division parameter) registered in ListToolsRequestSchema response.
    // Species & Assembly Information
    {
      name: 'list_species',
      description: 'Get list of available species and assemblies',
      inputSchema: {
        type: 'object',
        properties: {
          division: { type: 'string', description: 'Ensembl division (e.g., vertebrates, plants, fungi)' },
        },
        required: [],
      },
  • TypeScript interface defining the structure of Ensembl species data returned by the list_species tool.
    interface EnsemblSpecies {
      name: string;
      display_name: string;
      taxonomy_id: number;
      assembly: string;
      release: number;
      division: string;
      strain?: string;
      strain_collection?: string;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'Get' operation (implying read-only), but doesn't mention any behavioral traits like rate limits, authentication requirements, pagination, response format, or what 'available' means in context. The description is too minimal 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.

Conciseness5/5

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

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a simple list operation and gets straight to the point 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 insufficient. It doesn't explain what information is returned about species and assemblies, how results are structured, or any limitations. Given the complexity of biological data and the lack of structured documentation, more context is needed for an agent to use this effectively.

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 has 100% description coverage for its single parameter 'division', so the description doesn't need to add parameter details. The description doesn't mention the parameter at all, which is acceptable given the schema coverage. Baseline 3 is appropriate when the schema does the documentation work.

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 the resource 'list of available species and assemblies', making the purpose understandable. It doesn't explicitly differentiate from siblings like 'get_assembly_info' which might provide similar information, but the focus on 'available species' provides reasonable distinction.

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 like 'get_assembly_info' or 'batch_gene_lookup'. There's no mention of prerequisites, typical use cases, or limitations that would help an agent choose between this and sibling tools.

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/Augmented-Nature/Ensembl-MCP-Server'

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