Skip to main content
Glama
berntpopp
by berntpopp

Get Meta-Domain Variants

get_meta_domain
Read-onlyIdempotent

Retrieve homologous variant evidence (gnomAD and ClinVar) for a protein residue across its Pfam domain family, using transcript ID and position.

Instructions

Return homologous (meta-domain) variant evidence for one residue: gnomAD normal_variants and ClinVar pathogenic_variants observed at the aligned consensus position across the residue's Pfam domain family, each carrying its homolog gene_name. Omit domains to derive the selector from the residue's cached domain mapping; a residue with no meta-domain returns empty lists (not an error). Requires a built landscape. Signature: get_meta_domain(transcript_id=, position=, domains=, limit=, offset=, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transcript_idYesA versioned Ensembl transcript id (the .N version suffix is required), e.g. ENST00000269305.4. Resolve a gene symbol with resolve_transcript first.
positionYes1-based protein residue position.
domainsNoOptional meta-domain selector {PfamID: [consensus_pos, ...]}. Omit to derive it from the residue's cached domain mapping.
limitNoMaximum rows to return (1..1000; default 200).
offsetNoZero-based offset into the result list (for paging).
response_modeNoVerbosity: minimal|compact|standard|full (default compact).compact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYes
_metaNo
error_codeNo
messageNo
retryableNo
recovery_actionNo
fieldNo
hintNo
candidatesNo
recommended_citationNo
data_versionsNo
transcript_idNo
protein_positionNo
requested_domainsNo
meta_domainsNo
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds valuable behavioral details: omitting domains derives from cached mapping, empty lists for no meta-domain, and the requirement for a built landscape. 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?

The description is a single dense sentence that packs key information without redundancy. It could be slightly restructured for readability, but it is efficient.

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?

Given the tool's complexity (6 parameters, output schema present, rich annotations), the description covers return structure, handling of edge cases (no meta-domain), and prerequisites. Output schema covers return values, so no gaps.

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%, so baseline is 3. The description adds extra context for the 'domains' parameter (how omitting it works) and provides a signature line that summarizes all parameters. This goes beyond the schema alone.

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 returns homologous variant evidence for one residue, combining gnomAD and ClinVar data across Pfam domains. It distinguishes from siblings like get_protein_domains by focusing on meta-domain variant aggregation.

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

Usage Guidelines4/5

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

The description includes the tool's signature and prerequisites (requires built landscape), indicating when to use. It does not explicitly mention when not to use or alternatives, but the context is clear enough for an agent to decide.

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/berntpopp/metadome-link'

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