Skip to main content
Glama

uniprot_resolve_clinvar

Read-only

Fetch ClinVar records for a gene encoded by a UniProt entry, returning clinical significance, review status, and condition list. Optionally filter by protein change.

Instructions

Look up ClinVar records for the gene encoded by a UniProt entry. First fetches the entry to extract the canonical gene symbol, then queries NCBI eutils ClinVar by gene (and optional protein-change filter, e.g. R175H). Returns clinical-significance classification, review status, condition list (trait_set), molecular consequence, and the protein-change list per record.

Critical for clinical workflows — UniProt's natural-variant annotations stop at literature-described variants. ClinVar carries every variant submitted by clinical labs, with curated significance classifications. Combine uniprot_lookup_variant (UniProt side) with uniprot_resolve_clinvar (population side) for a full variant-effect picture.

Calls https://eutils.ncbi.nlm.nih.gov — declared in PRIVACY.md.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoMaximum number of ClinVar records to return; capped at 50.
changeNoOptional HGVS-shorthand protein change to filter to, e.g. 'R175H'. Leave empty to return all ClinVar records for the gene.
accessionYesUniProt accession, e.g. 'P04637' (human TP53) or 'P38398' (human BRCA1). Both reviewed (Swiss-Prot) and unreviewed (TrEMBL) accessions are accepted; case-sensitive.
response_formatNo'markdown' (default) for a human-readable report with a provenance footer, or 'json' for a machine-parseable structured payload with the same data. Any other value is rejected.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already indicate readOnly and openWorld hints; description adds details about fetching entry, querying NCBI, and external dependency, with no contradictions.

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?

Well-structured in paragraphs with front-loaded purpose; every sentence contributes meaningful information without redundancy.

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

Completeness5/5

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

With output schema present, description still explains return fields (significance, review status, etc.) and covers external API usage, making it complete for the tool's complexity.

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

Parameters4/5

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

Schema coverage is 100%, but description supplements with examples (e.g., 'R175H' for change), explains response_format options, and notes size cap at 50, adding value beyond 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?

Description clearly states it looks up ClinVar records for a gene encoded by a UniProt entry, distinguishing it from sibling tools like uniprot_lookup_variant by specifying it handles population-side variants.

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?

Explicitly mentions it is critical for clinical workflows because UniProt annotations are limited, and advises combining with uniprot_lookup_variant for a complete picture. Also notes external API call and privacy declaration.

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/smaniches/uniprot-mcp'

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