Skip to main content
Glama

ensembl_meta

Retrieve Ensembl server metadata, species information, data releases, and system status to access genomic database details and version tracking.

Instructions

Get server metadata, data releases, species info, and system status. Covers /info/* endpoints and /archive/id for version tracking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
info_typeNoType of information to retrieve
speciesNoSpecies name (required for species-specific info) (e.g., 'homo_sapiens', 'mus_musculus', 'drosophila_melanogaster')
archive_idNoID to get version information for (alternative to info_type) (e.g., 'ENSG00000141510', 'rs699')
divisionNoEnsembl division name (e.g., 'vertebrates', 'plants', 'fungi', 'metazoa')

Implementation Reference

  • The handleMeta function executes the core logic for the ensembl_meta tool by normalizing inputs and delegating to the Ensembl API client for metadata retrieval.
    export async function handleMeta(args: any) {
      try {
        const normalizedArgs = normalizeEnsemblInputs(args);
        return await ensemblClient.getMetaInfo(normalizedArgs);
      } catch (error) {
        return {
          error: error instanceof Error ? error.message : "Unknown error",
          success: false,
        };
      }
    }
  • Input schema and metadata definition for the ensembl_meta tool, defining parameters like info_type, species, archive_id.
    {
      name: "ensembl_meta",
      description:
        "Get server metadata, data releases, species info, and system status. Covers /info/* endpoints and /archive/id for version tracking.",
      inputSchema: {
        type: "object",
        properties: {
          info_type: {
            type: "string",
            enum: [
              "ping",
              "rest",
              "software",
              "data",
              "species",
              "divisions",
              "assembly",
              "biotypes",
              "analysis",
              "external_dbs",
              "variation",
            ],
            description: "Type of information to retrieve",
          },
          species: {
            type: "string",
            description:
              "Species name (required for species-specific info) (e.g., 'homo_sapiens', 'mus_musculus', 'drosophila_melanogaster')",
          },
          archive_id: {
            type: "string",
            description:
              "ID to get version information for (alternative to info_type) (e.g., 'ENSG00000141510', 'rs699')",
          },
          division: {
            type: "string",
            description:
              "Ensembl division name (e.g., 'vertebrates', 'plants', 'fungi', 'metazoa')",
          },
        },
        anyOf: [{ required: ["info_type"] }, { required: ["archive_id"] }],
      },
    },
  • Core API client method getMetaInfo that implements the actual Ensembl REST API calls for various metadata endpoints based on info_type.
    async getMetaInfo(args: any): Promise<any> {
      const { info_type, species, archive_id, division } = args;
    
      if (archive_id) {
        return this.makeRequest(`/archive/id/${archive_id}`);
      }
    
      switch (info_type) {
        case "ping":
          return this.makeRequest("/info/ping");
        case "rest":
          return this.makeRequest("/info/rest");
        case "software":
          return this.makeRequest("/info/software");
        case "data":
          return this.makeRequest("/info/data");
        case "species":
          return this.makeRequest("/info/species");
        case "divisions":
          return this.makeRequest("/info/divisions");
        case "assembly":
          if (!species) throw new Error("Species required for assembly info");
          return this.makeRequest(`/info/assembly/${species}`);
        case "biotypes":
          if (!species) throw new Error("Species required for biotypes info");
          return this.makeRequest(`/info/biotypes/${species}`);
        case "analysis":
          if (!species) throw new Error("Species required for analysis info");
          return this.makeRequest(`/info/analysis/${species}`);
        case "external_dbs":
          if (!species) throw new Error("Species required for external_dbs info");
          return this.makeRequest(`/info/external_dbs/${species}`);
        case "variation":
          if (!species) throw new Error("Species required for variation info");
          return this.makeRequest(`/info/variation/${species}`);
        default:
          throw new Error(`Unknown info_type: ${info_type}`);
      }
    }
  • index.ts:47-51 (registration)
    Tool list registration handler that returns the ensemblTools array containing the ensembl_meta tool definition.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: ensemblTools,
      };
    });
  • index.ts:99-107 (registration)
    Dispatch registration in the main CallToolRequest handler that routes ensembl_meta calls to the handleMeta function.
    case "ensembl_meta":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(await handleMeta(args), null, 2),
          },
        ],
      };
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what information can be retrieved (metadata, releases, species info, status) and the endpoints covered, but doesn't mention rate limits, authentication requirements, response formats, or error conditions. The description is informative but lacks operational details.

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 perfectly concise with two sentences that each earn their place. The first sentence states the purpose comprehensively, and the second sentence provides important implementation context about the endpoints covered. No wasted words.

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?

For a 4-parameter tool with no annotations and no output schema, the description provides good purpose and endpoint context but lacks information about return values, error handling, and operational constraints. Given the complexity of the tool (multiple parameter combinations), more behavioral context would be helpful.

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 documents all parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., it doesn't explain parameter interactions or provide examples). Baseline 3 is appropriate when 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 tool's purpose with specific verbs ('Get server metadata, data releases, species info, and system status') and resources ('/info/* endpoints and /archive/id'), distinguishing it from sibling tools focused on compara, features, lookup, mapping, etc. It explicitly covers what information can be retrieved.

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

Usage Guidelines4/5

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

The description provides clear context by mentioning the specific API endpoints covered ('/info/* endpoints and /archive/id'), which helps understand when to use this tool. However, it doesn't explicitly state when NOT to use it or name alternatives among siblings, though the distinction is implied by the different tool names.

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/effieklimi/ensembl-mcp-server'

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