Skip to main content
Glama

vep_id_single

Annotate a single genetic variant by rs or COSM identifier with Ensembl VEP, retrieving predicted consequences, pathogenicity scores, and functional annotations.

Instructions

Annotate a single variant using an identifier (e.g., rs1234567, COSM476)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
speciesYesSpecies name (e.g., 'homo_sapiens', 'mus_musculus')homo_sapiens
variant_idYesVariant identifier (rs or COSM/COSV/CM IDs)
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)
Behavior1/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 fails to mention any side effects, error handling, authentication requirements, rate limits, or behavior for invalid identifiers. The description adds no value beyond the basic action.

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 a single sentence, which is concise. However, it lacks structure and for 20 parameters, it is too sparse, omitting important context about optional flags and output. It is neither overly verbose nor well-structured.

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

Completeness1/5

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

Given the tool's complexity (20 parameters, no output schema), the description is severely incomplete. It does not explain the many optional boolean flags, their effect, what the output contains, or how to interpret results. The agent would lack sufficient context to use the tool effectively.

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 20 parameters with descriptions. The tool description adds no parameter-level information beyond what is in the schema. Given full schema coverage, baseline 3 is appropriate.

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 action ('Annotate') and the resource ('a single variant using an identifier'), with specific examples (rs1234567, COSM476) that distinguish it from sibling tools that use other input types (e.g., HGVS, region). The 'single' qualifier differentiates from batch variants.

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 versus alternatives like vep_id_batch or vep_hgvs_single. The description does not mention prerequisites, limitations, or recommended use cases, leaving the agent to infer based solely on the tool name.

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