Skip to main content
Glama

vep_hgvs_single

Annotate a single variant using HGVS notation to retrieve functional effects, pathogenicity scores, and protein domain information.

Instructions

Annotate a single variant using HGVS notation (genomic g., coding c., protein p.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
speciesYesSpecies name (e.g., 'homo_sapiens', 'mus_musculus')homo_sapiens
hgvs_notationYesHGVS notation (e.g., 'ENST00000366667:c.803C>T', '17:g.41276107A>C', 'ENSP00000401091.1:p.Tyr124Cys')
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?

No annotations are provided, so the description carries full burden. It only states 'annotate' without describing expected behavior, side effects, or output format. It lacks details on whether it's read-only, rate limits, or data source.

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 sentence (92 characters) that is concise and front-loaded with the core action. However, it sacrifices some completeness for brevity.

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 20 parameters, no output schema, and no annotations, the description is too minimal. It fails to explain high-level context like what VEP does, which annotations are returned, or how optional parameters affect output.

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 coverage is 100%, so the baseline is 3. The description adds no additional parameter-specific meaning beyond the schema, such as interactions or usage tips.

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 verb 'annotate' and the resource 'a single variant', and specifies the input format as HGVS notation. It distinguishes from batch tools but does not explicitly differentiate from other single-variant tools like vep_id_single.

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 vs. siblings (e.g., batch tools or vep_id_single). The description does not include any context on prerequisites or when to avoid using this tool.

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