Skip to main content
Glama

vep_region_single

Annotate a genetic variant by providing genomic region and allele, retrieving effect predictions including pathogenicity scores, conservation, and regulatory features.

Instructions

Annotate a variant using genomic region and allele

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
speciesYesSpecies name (e.g., 'homo_sapiens', 'mus_musculus')homo_sapiens
regionYesGenomic region (pos or range, optionally with allele)
alleleYesAllele base (A,C,G,T)
canonicalNoInclude only canonical transcripts per gene
hgvsNoInclude HGVS nomenclature
domainsNoInclude protein domain information
ccdsNoInclude CCDS transcript identifiers
proteinNoInclude protein sequence identifiers
AlphaMissenseNoInclude AlphaMissense pathogenicity scores
CADDNoInclude CADD deleteriousness scores
REVELNoInclude REVEL pathogenicity scores
ClinPredNoInclude ClinPred pathogenicity predictions
ConservationNoInclude conservation scores
Blosum62NoInclude BLOSUM62 substitution scores
GONoInclude Gene Ontology annotations
PhenotypesNoInclude phenotype data
tslNoInclude transcript support level
apprisNoInclude APPRIS annotations
maneNoInclude MANE transcript annotations
distanceNoDistance for regulatory features (bp, 0-5000000)
SpliceAINoSpliceAI score threshold (0-1)
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It does not mention that this tool handles only single variants, or what happens with defaults (e.g., all extra annotation flags default to false). The description adds no behavioral context beyond the schema.

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

Conciseness3/5

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

The description is only 5 words, which is concise but arguably under-informative. A single sentence is acceptable, but given the tool's complexity, more detail would be warranted without becoming verbose.

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?

With 21 parameters and no output schema, the description is too short to provide complete context. It does not describe return values, data sources, or any limitations. The schema descriptions are thorough, but the description itself adds minimal contextual 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 baseline is 3. The description 'using genomic region and allele' loosely echoes the required parameters but adds no new semantic meaning beyond what the schema already provides. The many optional parameters are not explained in the description.

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 ('Annotate a variant') and the primary inputs ('using genomic region and allele'), matching the required parameters. However, it does not differentiate from sibling tools like vep_hgvs_single or vep_id_single, which also annotate variants but with different input formats.

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?

No guidance is provided on when to use this tool over siblings. The description lacks any indication of suitable scenarios, exclusions, or alternatives. For example, vep_region_batch is for batch queries, but this tool's single-query nature is not mentioned.

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/not-a-feature/VEPmcp'

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