Skip to main content
Glama

get_variant_annotations

Retrieve comprehensive biological annotation values for a genetic variant, including reference and alternate allele predictions across 325 annotations. Filter by category for targeted analysis.

Instructions

Get detailed annotation probe values for a variant.

Returns the Evo 2 model's predicted annotation values for both the reference and alternate allele across 325 biological annotations. Each annotation shows ref (reference allele prediction), alt (alternate allele prediction), and delta (alt - ref).

Use this for deep analysis when you need the full picture — e.g., all chromatin marks across tissues, all amino acid probabilities, or every protein feature prediction. For a quick ranked view of what's most disrupted, use get_variant_disruptions instead.

Args: variant_id: Variant identifier in chr:pos:ref:alt format. category: Optional filter. One of: amino_acid, atacseq, ccre, chipseq, chromhmm, elm, fstack, protein_feature, interpro, genomic_feature, ptm, region, secondary_structure. Omit to get ALL annotations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
variant_idYes
categoryNo
Behavior4/5

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

No annotations, but description fully explains output structure (ref, alt, delta per annotation) and parameter details. No mention of side effects or auth, but read-only nature is implicit.

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?

Well-structured with clear paragraphs, bullet-like list for categories, and no redundant sentences. Efficiently conveys all necessary information.

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

Completeness5/5

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

Covers both parameters, explains return structure (325 annotations with ref/alt/delta), provides category filter details, and references sibling tool. Complete for a read-only query tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description adds valuable semantics: variant_id format (chr:pos:ref:alt) and lists category options with example values, compensating fully.

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?

Description clearly states it gets 'detailed annotation probe values for a variant', specifies ref, alt, delta fields, and distinguishes from sibling get_variant_disruptions which offers quick ranked view.

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?

Explicitly says 'use this for deep analysis' and advises to use get_variant_disruptions for quick ranked view, providing clear when-to-use and alternative.

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/goodfire-ai/evee-mcp'

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