Skip to main content
Glama
berntpopp
by berntpopp

Get Tolerance Landscape

get_tolerance_landscape
Read-onlyIdempotent

Retrieve per-residue missense tolerance, variant counts, and Pfam domain annotations for a human transcript. Optionally specify an inclusive residue range to focus on a region.

Instructions

Return the (cache-first) MetaDome tolerance landscape for a built transcript: Pfam domains plus the paginated per-residue positional_annotation (sw_dn_ds tolerance, variant counts). Optional position_start/position_stop slice an inclusive residue range. If the build is still running this returns a first-class status='processing' success -- poll again after poll_after_s. Signature: get_tolerance_landscape(transcript_id=, position_start=, position_stop=, 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.
position_startNo
position_stopNo
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
gene_nameNo
protein_acNo
refseq_idsNo
domainsNo
positional_annotationNo
paginationNo
statusNo
poll_after_sNo
Behavior4/5

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

Annotations already indicate read-only, idempotent, and open-world. The description adds valuable behavioral details: cache-first behavior, returning 'status=processing' for unfinished builds, and polling guidance. No contradictions with annotations.

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 informative and structured, front-loading the main purpose. However, it is somewhat verbose with technical terms and includes the full signature, which could be omitted for conciseness.

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 (6 parameters, output schema present), the description covers key behaviors: caching, processing state, pagination, response modes, and prerequisite to resolve transcripts. It is complete enough for effective use.

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 high (all 6 parameters have descriptions). The description re-iterates some schema info (e.g., optional range slice) but does not add significant new meaning beyond what the schema provides. It includes the function signature, which is redundant.

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 a tolerance landscape for a built transcript, including Pfam domains and per-residue positional annotation. It distinguishes from siblings like get_protein_domains (domains only) and get_position_tolerance (single position) by specifying the scope and content.

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 provides usage context (cache-first, polling if processing, optional range slicing) but does not explicitly contrast with sibling tools or state when to use this tool over alternatives. It gives a signature but lacks exclusions.

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