Skip to main content
Glama

biothings_get_variant

Retrieve detailed annotation data for a single variant using its HGVS or rsID identifier. Ideal when you already know the variant ID and need precise data without complex search filters.

Instructions

Fetch a specific variant by HGVS or rsID.

    Retrieves detailed annotation data for a **single, specific variant** using its identifier.
    **This is the preferred tool over `query_variants` for fetching a specific variant when you already know 
    its standard ID (HGVS or rsID) and don't need complex search filters.**
    
    **Supported Identifiers:**
    - HGVS ID (e.g., `chr7:g.140453134T>C`). *Note: MyVariant.info primarily uses hg19-based HGVS IDs.*
    - dbSNP rsID (e.g., `rs58991260`)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
fieldsNoall
variant_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoVariant identifier
vcfNoVCF information
caddNoCADD scores and predictions
docmNoDoCM annotations
hg19NoHG19 genomic location
chromNoChromosome number
dbsnpNodbSNP annotations
mutdbNoMutDB annotations
cosmicNoCOSMIC annotations
dbnsfpNodbNSFP functional predictions
snpeffNoSnpEff annotations
clinvarNoClinVar annotations
versionNoVersion number
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool retrieves detailed annotation data, which implies a read operation. It also notes the hg19 base for HGVS IDs, a useful behavioral nuance. However, it does not mention any authorization requirements, rate limits, or that it is a read-only operation explicitly.

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 well-structured with sections and bullet points, making it easy to scan. It is concise but contains some redundancy (e.g., repeating 'specific variant' multiple times). Overall, it is efficient and front-loaded.

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?

Given that an output schema exists (not visible) and the tool has 3 parameters, the description covers the main purpose and the key parameter well. However, the lack of documentation for `email` and `fields` reduces completeness. For a single-variant fetch tool, it is adequate but not fully comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description only explains the `variant_id` parameter with examples and notes. The `email` and `fields` parameters are completely undocumented in the description, leaving the agent without guidance on how to use them.

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 explicitly states it fetches a specific variant by HGVS or rsID, and distinguishes itself from the sibling tool `query_variants` by emphasizing it is for single, specific identifiers. The verb 'Fetch' and resource 'variant' are clear, and the scope is well-defined.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: 'This is the preferred tool over query_variants for fetching a specific variant when you already know its standard ID.' It also lists supported identifiers, giving clear context for when to use this tool instead of alternatives.

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/longevity-genie/biothings-mcp'

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