Skip to main content
Glama

alphagenome_predictor

Predict regulatory effects of genetic variants on gene expression, chromatin accessibility, splicing, and promoter activity using AlphaGenome. Requires an API key and integration with BioMCP for variant interpretation.

Instructions

Predict variant effects on gene regulation using Google DeepMind's AlphaGenome.

⚠️ PREREQUISITE: Use the 'think' tool FIRST to plan your analysis strategy!

AlphaGenome provides state-of-the-art predictions for how genetic variants
affect gene regulation, including:
- Gene expression changes (RNA-seq)
- Chromatin accessibility impacts (ATAC-seq, DNase-seq)
- Splicing alterations
- Promoter activity changes (CAGE)

This tool requires:
1. AlphaGenome to be installed (see error message for instructions)
2. An API key from https://deepmind.google.com/science/alphagenome

API Key Options:
- Provide directly via the api_key parameter
- Or set ALPHAGENOME_API_KEY environment variable

Example usage:
- Predict regulatory effects of BRAF V600E mutation: chr7:140753336 A>T
- Assess non-coding variant impact on gene expression
- Evaluate promoter variants in specific tissues

Note: This is an optional tool that enhances variant interpretation
with AI predictions. Standard annotations remain available via variant_getter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
alternateYesAlternate allele(s) (e.g., 'T', 'A')
api_keyNoAlphaGenome API key. Check if user mentioned 'my AlphaGenome API key is...' in their message. If not provided here and no env var is set, user will be prompted to provide one.
chromosomeYesChromosome (e.g., 'chr7', 'chrX')
interval_sizeNoSize of genomic interval to analyze in bp (max 1,000,000)
positionYes1-based genomic position of the variant
referenceYesReference allele(s) (e.g., 'A', 'ATG')
significance_thresholdNoThreshold for significant log2 fold changes (default: 0.5)
tissue_typesNoUBERON ontology terms for tissue-specific predictions (e.g., 'UBERON:0002367' for external ear)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/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 effectively describes prerequisites (installation, API key), authentication needs (API key options), and context (enhances variant interpretation with AI predictions). However, it lacks details on rate limits, error handling, or what the output contains, leaving some behavioral aspects unclear.

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 well-structured with sections for prerequisites, capabilities, requirements, API key options, examples, and notes. It is appropriately sized for a complex tool, but some sentences could be more front-loaded (e.g., the prerequisite warning is prominent, but the core purpose is slightly buried). Overall, it earns its place with useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, no annotations, and an output schema (which handles return values), the description is mostly complete. It covers purpose, usage, prerequisites, and examples, but could improve by detailing output format or error scenarios. The presence of an output schema reduces the need to explain returns, but more behavioral context would enhance completeness.

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 8 parameters thoroughly. The description adds minimal parameter-specific semantics beyond the schema, such as implying variant input format in examples (e.g., 'chr7:140753336 A>T') and mentioning tissue-specific predictions. This meets the baseline of 3 when schema coverage is high.

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: 'Predict variant effects on gene regulation using Google DeepMind's AlphaGenome.' It specifies the verb ('predict'), resource ('variant effects on gene regulation'), and technology ('AlphaGenome'), distinguishing it from sibling tools like variant_getter or variant_searcher that handle standard annotations rather than AI predictions.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: it states a prerequisite ('Use the 'think' tool FIRST to plan your analysis strategy!'), gives examples of when to use it (e.g., 'Predict regulatory effects of BRAF V600E mutation'), and contrasts it with alternatives ('Standard annotations remain available via variant_getter'). This covers when to use, when not to use, and alternatives clearly.

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

Related 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/genomoncology/biomcp'

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