Skip to main content
Glama

vep_hgvs_batch

Annotate multiple genetic variants in batch by providing HGVS notations to retrieve comprehensive variant effect predictions including pathogenicity scores, protein domains, and conservation from Ensembl VEP.

Instructions

Annotate multiple variants using HGVS notation in batch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
speciesYesSpecies name (e.g., 'homo_sapiens', 'mus_musculus')homo_sapiens
hgvs_notationsYesList of HGVS notations (e.g., ['ENST00000366667:c.803C>T', '9:g.22125504G>C'])
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
ConservationNoInclude conservation scores
Behavior2/5

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

With no annotations, the description does not disclose behavioral traits such as error handling for invalid HGVS, performance expectations, or data source details.

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?

Single sentence, clear, no redundant information.

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

Completeness3/5

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

The description is minimal but covers the core purpose; however, it lacks explanation of return values or behavior, and no output schema is provided.

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?

Input schema has 100% coverage with descriptions for all 11 parameters; the description adds no extra semantic value beyond the schema.

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 annotates multiple variants using HGVS notation in batch, distinguishing it from single-variant and other batch tools.

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

Usage Guidelines3/5

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

The description implies batch processing but does not explicitly guide when to use this tool versus alternatives like vep_hgvs_single or other VEP tools.

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