Skip to main content
Glama
Augmented-Nature

Ensembl MCP Server

get_assembly_info

Retrieve genome assembly details and statistics for species, including chromosome banding patterns when specified.

Instructions

Get genome assembly information and statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
speciesNoSpecies name (default: homo_sapiens)
bandsNoInclude chromosome banding patterns (default: false)

Implementation Reference

  • src/index.ts:778-788 (registration)
    Registration of the get_assembly_info tool in the ListToolsRequestSchema response, defining its name, description, and input schema.
      name: 'get_assembly_info',
      description: 'Get genome assembly information and statistics',
      inputSchema: {
        type: 'object',
        properties: {
          species: { type: 'string', description: 'Species name (default: homo_sapiens)' },
          bands: { type: 'boolean', description: 'Include chromosome banding patterns (default: false)' },
        },
        required: [],
      },
    },
  • src/index.ts:871-872 (registration)
    Maps the tool name to its handler function in the CallToolRequestSchema switch statement.
    case 'get_assembly_info':
      return this.handleGetAssemblyInfo(args);
  • The handler function that executes the tool: validates args, fetches data from Ensembl REST API endpoint `/info/assembly/{species}`, formats response as JSON, handles errors.
    private async handleGetAssemblyInfo(args: any) {
      if (!isValidAssemblyArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid assembly info arguments');
      }
    
      try {
        const species = this.getDefaultSpecies(args.species);
    
        const params: any = {};
    
        if (args.bands) {
          params.bands = 1;
        }
    
        const response = await this.apiClient.get(`/info/assembly/${species}`, { params });
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        return this.handleError(error, 'fetching assembly info');
      }
    }
  • Input validation type guard used in the handler to ensure arguments conform to expected schema.
    const isValidAssemblyArgs = (
      args: any
    ): args is { species?: string; bands?: boolean } => {
      return (
        typeof args === 'object' &&
        args !== null &&
        (args.species === undefined || typeof args.species === 'string') &&
        (args.bands === undefined || typeof args.bands === 'boolean')
      );
    };
  • TypeScript interface matching the expected response structure from the Ensembl assembly info API.
    interface EnsemblAssemblyInfo {
      assembly_name: string;
      assembly_date: string;
      assembly_accession: string;
      genebuild_last_geneset_update: string;
      genebuild_initial_release_date: string;
      genebuild_start_date: string;
      genebuild_version: string;
      genebuild_method: string;
      golden_path_length: number;
      total_coding_sequence_length: number;
      total_genome_length: number;
      coord_system_versions: string[];
      karyotype: string[];
    }
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. It only states what the tool does ('Get genome assembly information and statistics') without mentioning important behavioral aspects like whether this is a read-only operation, what format the information comes in, potential rate limits, or authentication requirements.

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 communicates the core purpose without any wasted words. It's appropriately sized for a simple retrieval tool and gets straight to the point.

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 and statistics' includes, what format the results come in, or any behavioral constraints. Given the lack of structured metadata, the description should provide more complete context about what this tool actually returns.

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 description adds no parameter-specific information beyond what's already in the schema (which has 100% coverage). It doesn't explain what 'genome assembly information and statistics' includes or how parameters affect the output. With complete schema coverage, the baseline is 3 even without additional parameter context.

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 action ('Get') and resource ('genome assembly information and statistics'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'get_karyotype' or 'list_species' that might also provide assembly-related information, preventing a perfect score.

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 sibling tools like 'get_karyotype' and 'list_species' that might overlap in functionality, there's no indication of what distinguishes this tool or when it should be preferred over others.

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