Skip to main content
Glama
shukwong

gnomAD MCP Server

by shukwong

get_transcript

Retrieve detailed genetic information for a specific Ensembl transcript ID from the gnomAD database, including variant data and population genetics insights.

Instructions

Get information about a specific transcript

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transcript_idYesEnsembl transcript ID (e.g., ENST00000269305)
reference_genomeNoReference genomeGRCh38

Implementation Reference

  • The main handler function for the 'get_transcript' tool. It parses the input arguments, makes a GraphQL request using the predefined query, and formats the response.
    case "get_transcript":
      result = await makeGraphQLRequest(QUERIES.getTranscript, {
        transcriptId: args.transcript_id as string,
        referenceGenome: parseReferenceGenome((args.reference_genome as string) || "GRCh38"),
      });
      formattedResult = result.data?.transcript || null;
      break;
  • GraphQL query schema definition for fetching transcript details including location, gene info, and gnomAD constraint metrics.
    getTranscript: `
      query GetTranscript($transcriptId: String!, $referenceGenome: ReferenceGenomeId!) {
        transcript(transcript_id: $transcriptId, reference_genome: $referenceGenome) {
          transcript_id
          transcript_version
          reference_genome
          chrom
          start
          stop
          strand
          gene_id
          gene_symbol
          gene_version
          gnomad_constraint {
            exp_lof
            exp_mis
            exp_syn
            obs_lof
            obs_mis
            obs_syn
            oe_lof
            oe_lof_lower
            oe_lof_upper
            oe_mis
            oe_mis_lower
            oe_mis_upper
            oe_syn
            oe_syn_lower
            oe_syn_upper
            lof_z
            mis_z
            syn_z
            pLI
          }
        }
      }
    `,
  • src/index.ts:507-525 (registration)
    Tool registration in the ListTools handler, defining name, description, and input schema for validation.
    {
      name: "get_transcript",
      description: "Get information about a specific transcript",
      inputSchema: {
        type: "object",
        properties: {
          transcript_id: {
            type: "string",
            description: "Ensembl transcript ID (e.g., ENST00000269305)",
          },
          reference_genome: {
            type: "string",
            description: "Reference genome",
            default: "GRCh38",
          },
        },
        required: ["transcript_id"],
      },
    },
  • Input schema for the get_transcript tool, specifying required transcript_id and optional reference_genome.
    inputSchema: {
      type: "object",
      properties: {
        transcript_id: {
          type: "string",
          description: "Ensembl transcript ID (e.g., ENST00000269305)",
        },
        reference_genome: {
          type: "string",
          description: "Reference genome",
          default: "GRCh38",
        },
      },
      required: ["transcript_id"],
    },
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 retrieves information, implying a read-only operation, but does not specify permissions, rate limits, error conditions, or output format. This leaves significant gaps in understanding how the tool behaves beyond basic functionality.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single, efficient sentence ('Get information about a specific transcript') that is front-loaded and wastes no words. However, it is overly concise, bordering on under-specified, which slightly reduces its effectiveness despite the clean structure.

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 (retrieving transcript information), lack of annotations, and no output schema, the description is incomplete. It does not explain what information is returned, error handling, or behavioral traits, making it inadequate for an agent to fully understand the tool's context and usage.

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 input schema fully documents both parameters ('transcript_id' and 'reference_genome'). The description adds no additional meaning beyond what the schema provides, such as examples or constraints, resulting in a baseline score of 3 as the schema handles parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose ('Get information about a specific transcript'), which is clear but vague. It specifies the verb ('Get') and resource ('transcript'), but does not distinguish what type of information is retrieved or how it differs from sibling tools like 'get_gene' or 'get_variant', leaving the scope ambiguous.

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 does not mention prerequisites, exclusions, or compare to siblings such as 'get_gene' or 'get_variants_in_gene', leaving the agent to infer usage context without explicit direction.

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