Skip to main content
Glama
Augmented-Nature

Ensembl MCP Server

map_coordinates

Convert genomic coordinates between different genome assemblies to align data across versions or species.

Instructions

Convert coordinates between genome assemblies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionYesGenomic region (chr:start-end)
speciesNoSpecies name (default: homo_sapiens)
target_assemblyYesTarget assembly name

Implementation Reference

  • The handler function for the 'map_coordinates' tool. It fetches coordinate mappings from the Ensembl REST API /map/coords endpoint, converting genomic regions between different assembly versions. Uses helper methods getDefaultSpecies and formatGenomicRegion.
    private async handleMapCoordinates(args: any) {
      try {
        const species = this.getDefaultSpecies(args.species);
        const region = this.formatGenomicRegion(args.region);
    
        const response = await this.apiClient.get(`/map/coords/${species}/${args.target_assembly}/${region}`);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        return this.handleError(error, 'mapping coordinates');
      }
  • src/index.ts:753-764 (registration)
    Tool registration in the ListToolsRequestSchema handler. Defines the name, description, and input schema for the map_coordinates tool.
      name: 'map_coordinates',
      description: 'Convert coordinates between genome assemblies',
      inputSchema: {
        type: 'object',
        properties: {
          region: { type: 'string', description: 'Genomic region (chr:start-end)' },
          species: { type: 'string', description: 'Species name (default: homo_sapiens)' },
          target_assembly: { type: 'string', description: 'Target assembly name' },
        },
        required: ['region', 'target_assembly'],
      },
    },
  • Type guard function for validating input arguments to the map_coordinates tool, though not called in the handler.
    const isValidMapCoordinatesArgs = (
      args: any
    ): args is { region: string; species?: string; target_assembly: string } => {
      return (
        typeof args === 'object' &&
        args !== null &&
        typeof args.region === 'string' &&
        args.region.length > 0 &&
        (args.species === undefined || typeof args.species === 'string') &&
        typeof args.target_assembly === 'string' &&
        args.target_assembly.length > 0
      );
    };
  • src/index.ts:866-867 (registration)
    Dispatch case in the CallToolRequestSchema switch statement that routes calls to the map_coordinates handler.
    case 'map_coordinates':
      return this.handleMapCoordinates(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's function but lacks critical behavioral details: it doesn't specify if this is a read-only operation (likely, but not confirmed), what the output format is (since no output schema exists), potential rate limits, error conditions (e.g., invalid assemblies), or whether it's a batch or single conversion. 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 directly states the tool's purpose without any fluff or redundant information. It's front-loaded with the core action ('Convert coordinates'), making it immediately clear. Every word earns its place, and there's no waste or 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?

Given the tool's complexity (coordinate conversion between genome assemblies is a non-trivial genomic operation), lack of annotations, and absence of an output schema, the description is insufficiently complete. It doesn't explain what the tool returns (e.g., mapped coordinates, errors), behavioral traits like idempotency or side effects, or usage context. For a tool with no structured output or annotations, the description should provide more context to guide the agent 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 description coverage is 100%, meaning all parameters are documented in the schema itself (e.g., 'region' as 'Genomic region (chr:start-end)'). The description adds no additional parameter semantics beyond the schema, such as examples, format constraints, or default behaviors for optional parameters like 'species'. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't enhance parameter understanding but doesn't need to compensate for gaps.

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 specific action ('Convert coordinates') and the resource involved ('between genome assemblies'). It precisely distinguishes this tool from all sibling tools, which perform different genomic operations like gene lookup, sequence fetching, or variant analysis, none of which involve coordinate conversion between assemblies.

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. While it's clear from the purpose that this is for coordinate conversion, there's no mention of prerequisites (e.g., needing a source assembly), exclusions, or related tools like 'get_assembly_info' that might provide assembly details. The agent must infer usage solely from the tool name and parameters.

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