VEPmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vep_hgvs_singleC | Annotate a single variant using HGVS notation (genomic g., coding c., protein p.) |
| vep_hgvs_batchA | Annotate multiple variants using HGVS notation in batch |
| vep_id_singleC | Annotate a single variant using an identifier (e.g., rs1234567, COSM476) |
| vep_id_batchC | Annotate multiple variants using identifiers in batch |
| vep_region_singleC | Annotate a variant using genomic region and allele |
| vep_region_batchB | Annotate multiple variants using genomic coordinates in batch |
| get_vep_speciesA | Get list of available species for VEP annotation |
| get_consequence_typesA | Get available VEP consequence types and descriptions |
| get_assembly_infoB | Get genome assembly information for a species |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct action and input type. The three 'get_' tools retrieve metadata, while the six 'vep_' tools annotate variants and are clearly separated by input format (HGVS, ID, region) and batching mode. No two tools overlap in purpose.
Naming follows a consistent pattern: 'get_' for informational queries and 'vep_<format>_<mode>' for annotation tools. All names use snake_case and clearly convey the action and target resource, making the set predictable.
With nine tools, the server is well-scoped for its domain. The three metadata tools and six annotation tools (covering three input formats, each with batch and single variants) provide a complete set without excessive or insufficient endpoints.
The tool set covers core VEP functionality: metadata retrieval (assembly, consequences, species) and annotation via common input formats (HGVS, identifiers, regions) with both single and batch modes. No obvious gaps exist for a standard VEP annotation server.