Skip to main content
Glama
berntpopp
by berntpopp

Summarize Intolerant Regions

summarize_intolerant_regions
Read-onlyIdempotent

Identify the most constrained protein regions from MetaDome tolerance landscapes. Returns stretches of residues with low tolerance scores, annotated with Pfam domains and variant counts.

Instructions

Return the top ranked contiguous intolerant regions of a MetaDome tolerance landscape, each annotated with overlapping Pfam domain ids and aggregate gnomAD/ClinVar variant counts. Regions are stretches of consecutive residues with sw_dn_ds below threshold (length >= min_run), ranked by mean sw_dn_ds ascending (most constrained first). Signature: summarize_intolerant_regions(transcript_id, threshold=0.5, min_run=3, top_n=15, response_mode='compact').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_nNoMaximum number of regions to return, ranked by mean_sw_dn_ds ascending (default 15).
min_runNoMinimum number of consecutive residues to form a region (default 3). Shorter stretches are discarded.
thresholdNosw_dn_ds threshold (exclusive upper bound) for intolerant residues (default 0.5). Lower values identify only the most constrained positions.
response_modeNoVerbosity: minimal|compact|standard|full (default compact).compact
transcript_idYesA versioned Ensembl transcript id (the .N version suffix is required), e.g. ENST00000269305.4. Resolve a gene symbol with resolve_transcript first.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
_metaNo
fieldNo
top_nNo
messageNo
min_runNo
regionsNo
successYes
gene_nameNo
retryableNo
thresholdNo
candidatesNo
error_codeNo
region_countNo
data_versionsNo
transcript_idNo
recovery_actionNo
recommended_citationNo
Behavior4/5

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

Annotations declare readOnlyHint and idempotentHint true, which are consistent with the read-only nature. The description adds behavioral context: regions are defined by sw_dn_ds below threshold, minimum length, and ascending ranking. 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.

Conciseness5/5

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

Two sentences plus a signature line—extremely concise. The main purpose is front-loaded, and every sentence adds essential information. No wasted words.

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 5 parameters (1 required) and the presence of an output schema, the description adequately covers the tool's purpose, ranking logic, and parameter roles. It does not need to detail return values because the output schema exists.

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%, providing descriptions for each parameter. The description adds value by explaining how parameters interact (e.g., threshold is exclusive upper bound, ranking by mean sw_dn_ds) and provides a signature with defaults. This goes beyond the schema's standalone descriptions.

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 'top ranked contiguous intolerant regions' annotated with Pfam domains and variant counts, with a specific verb ('Return') and resource. It distinguishes itself from siblings like 'get_tolerance_landscape' by focusing on summarizing regions rather than fetching the full landscape.

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

Usage Guidelines3/5

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

The description implies usage for extracting intolerant regions with given thresholds but does not explicitly state when to use this tool over alternatives like 'compare_positions' or 'get_tolerance_landscape'. No direct comparisons or exclusions are provided.

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