Skip to main content
Glama

variant_searcher

Retrieve detailed genetic variant records, including population frequencies, clinical significance, and functional predictions, from MyVariant.info. Search by gene, HGVS notation, rsID, or genomic region, and filter by clinical or functional criteria to refine results.

Instructions

Search MyVariant.info for genetic variant DATABASE RECORDS.

⚠️ PREREQUISITE: Use the 'think' tool FIRST to plan your research strategy!

Important: This searches for variant DATABASE RECORDS (frequency, significance, etc.),
NOT articles about variants. For articles about variants, use article_searcher.

Searches the comprehensive variant database including:
- Population frequencies (gnomAD, 1000 Genomes, etc.)
- Clinical significance (ClinVar)
- Functional predictions (SIFT, PolyPhen, CADD)
- Gene and protein consequences

Search by various identifiers or filter by clinical/functional criteria.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cadd_score_minNoMinimum CADD score for pathogenicity
consequenceNoVariant consequence (e.g., 'missense_variant')
frequency_maxNoMaximum allele frequency
frequency_minNoMinimum allele frequency
geneNoGene symbol (e.g., 'BRAF', 'TP53')
hgvsNoHGVS notation (genomic, coding, or protein)
hgvscNoCoding sequence change (e.g., 'c.1799T>A')
hgvspNoProtein change in HGVS format (e.g., 'p.V600E')
include_cbioportalNoInclude cBioPortal cancer genomics summary when searching by gene
pageNoPage number (1-based)
page_sizeNoResults per page
polyphen_predictionNoPolyPhen-2 functional prediction
regionNoGenomic region (e.g., 'chr7:140753336-140753337')
rsidNodbSNP rsID (e.g., 'rs113488022')
sift_predictionNoSIFT functional prediction
significanceNoClinical significance filter

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/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 effectively describes what the tool searches (variant database records with specific data types like population frequencies and clinical significance) and mentions a prerequisite. However, it doesn't disclose potential limitations like rate limits, authentication needs, or pagination behavior (though pagination parameters exist in the schema).

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 clear sections: purpose, prerequisite, distinction from alternatives, and search scope. It uses bullet points effectively to list data categories. While slightly longer than minimal, every sentence adds value (prerequisite warning, sibling differentiation, scope clarification). The warning emoji draws attention appropriately.

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

Completeness4/5

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

Given the tool's complexity (16 parameters, no annotations, but with output schema), the description does a good job covering purpose, usage context, and behavioral aspects. The output schema existence means return values don't need explanation. The main gap is lack of explicit behavioral constraints (rate limits, auth), but the prerequisite warning and scope clarification provide substantial context.

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 16 parameters thoroughly. The description adds some context by listing categories of searchable data (population frequencies, clinical significance, etc.) which maps to parameter groups, but doesn't provide additional syntax or format details beyond what the schema provides. This meets the baseline for high schema coverage.

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 searches MyVariant.info for genetic variant database records, specifying it retrieves frequency, significance, and functional data rather than articles. It explicitly distinguishes from the sibling tool 'article_searcher' by stating 'NOT articles about variants.' The verb 'search' is specific and the resource 'MyVariant.info' is named.

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: it includes a prerequisite ('Use the 'think' tool FIRST to plan your research strategy!'), clarifies when NOT to use this tool ('NOT articles about variants'), and names the alternative tool ('article_searcher'). This gives clear context for when to use this tool versus other options.

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

Related 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/genomoncology/biomcp'

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