Skip to main content
Glama
berntpopp
by berntpopp

Get Position Tolerance

get_position_tolerance
Read-onlyIdempotent

Retrieve missense tolerance, Pfam domain affiliation, and variant counts for a specific protein residue position using a pre-built tolerance landscape.

Instructions

Return one residue's missense tolerance (sw_dn_ds + sliding-window coverage), its Pfam/meta-domain membership, and gnomAD/ClinVar variant counts on a built tolerance landscape. Out-of-range positions raise invalid_input; a not-yet-built landscape raises not_found (request_tolerance_landscape first). Signature: get_position_tolerance(transcript_id=, position=, 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.
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_posNo
ref_aaNo
sw_dn_dsNo
sw_coverageNo
sw_sizeNo
domain_idsNo
variant_count_totalNo
Behavior4/5

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

Annotations declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, which are consistent with a read operation. The description adds error behavior (invalid_input, not_found) and dependency on landscape building, providing context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences plus a concise signature; every sentence adds value with no redundancy. Front-loaded with main purpose and error handling.

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 output schema exists, the description sufficiently covers error conditions, prerequisites, and core functionality. Could reinforce the 1-based position and reliance on protein-coding transcripts, but overall adequate.

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 coverage is 100% with descriptions for all three parameters. The description adds a signature line and error context but does not significantly enhance parameter understanding beyond the schema. Baseline 3 is appropriate.

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 missense tolerance, Pfam/meta-domain membership, and variant counts for a specific residue, and distinguishes from siblings by referencing the need for a pre-built tolerance landscape and mentioning request_tolerance_landscape.

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 explicitly warns about out-of-range and not-yet-built landscape errors, implying the prerequisite of building the landscape first via request_tolerance_landscape. It also references resolve_transcript for transcript resolution in the schema. However, it doesn't explicitly name alternative tools.

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