Skip to main content
Glama
shukwong

gnomAD MCP Server

by shukwong

search

Query genetic variant data, gene constraints, and population frequencies from the Genome Aggregation Database. Search by gene symbol, variant ID, or genomic region to access detailed genetic information.

Instructions

Search for genes, variants, or regions in gnomAD

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query (gene symbol, gene ID, variant ID, rsID, etc.)
reference_genomeNoReference genome (GRCh37 or GRCh38)GRCh38
datasetNoDataset ID (gnomad_r4, gnomad_r3, gnomad_r2_1, etc.)gnomad_r4

Implementation Reference

  • The execution handler for the 'search' tool. It calls the GraphQL API with the searchGene query using the provided query and parsed reference genome.
    case "search":
      result = await makeGraphQLRequest(QUERIES.searchGene, {
        query: args.query as string,
        referenceGenome: parseReferenceGenome((args.reference_genome as string) || "GRCh38"),
      });
      formattedResult = result.data?.searchResults || [];
      break;
  • Input schema for the 'search' tool, defining parameters like query, reference_genome, and dataset.
    inputSchema: {
      type: "object",
      properties: {
        query: {
          type: "string",
          description: "Search query (gene symbol, gene ID, variant ID, rsID, etc.)",
        },
        reference_genome: {
          type: "string",
          description: "Reference genome (GRCh37 or GRCh38)",
          default: "GRCh38",
        },
        dataset: {
          type: "string",
          description: "Dataset ID (gnomad_r4, gnomad_r3, gnomad_r2_1, etc.)",
          default: "gnomad_r4",
        },
      },
      required: ["query"],
    },
  • src/index.ts:415-438 (registration)
    Registration of the 'search' tool in the ListTools response, including name, description, and input schema.
    {
      name: "search",
      description: "Search for genes, variants, or regions in gnomAD",
      inputSchema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description: "Search query (gene symbol, gene ID, variant ID, rsID, etc.)",
          },
          reference_genome: {
            type: "string",
            description: "Reference genome (GRCh37 or GRCh38)",
            default: "GRCh38",
          },
          dataset: {
            type: "string",
            description: "Dataset ID (gnomad_r4, gnomad_r3, gnomad_r2_1, etc.)",
            default: "gnomad_r4",
          },
        },
        required: ["query"],
      },
    },
  • GraphQL query template 'searchGene' used by the 'search' tool handler to perform the search.
    searchGene: `
      query SearchGene($query: String!, $referenceGenome: ReferenceGenomeId!) {
        searchResults(query: $query, referenceGenome: $referenceGenome) {
          label
          value: url
        }
      }
    `,
  • Helper function to parse and validate the reference genome parameter used in the 'search' handler.
    function parseReferenceGenome(genome: string): string {
      const validGenomes = ["GRCh37", "GRCh38"];
      if (!validGenomes.includes(genome)) {
        return "GRCh38"; // Default to GRCh38
      }
      return genome;
    }
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 searches but doesn't describe what the search returns (e.g., list of matches, details), how results are formatted, any limitations (e.g., pagination, rate limits), or authentication needs. This leaves significant gaps for an agent to understand the tool's behavior.

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 wasted words. It's front-loaded and appropriately sized for a search tool, making it easy for an agent to parse quickly.

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 complexity of a search tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the search returns, how results are structured, or any behavioral traits like error handling or performance. This leaves the agent with incomplete context for effective use.

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 fully documents all three parameters. The description adds no additional meaning beyond what's in the schema, such as examples of query formats or dataset differences. The baseline score of 3 reflects adequate coverage by the schema alone.

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 ('Search for') and the target resources ('genes, variants, or regions in gnomAD'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_gene' or 'get_variant', which appear to fetch specific items rather than perform broad searches.

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. It doesn't mention sibling tools or contexts where other tools might be more appropriate, such as using 'get_gene' for known gene symbols or 'get_variant' for specific variant IDs.

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/shukwong/gnomad-mcp-server'

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