Get per-residue missense tolerance, Pfam domains, and variant counts for a human transcript by providing its ENST ID. Choose from minimal to full response modes.
Signature: request_tolerance_landscape(transcript_id, response_mode=).
| Name | Required | Description | Default |
|---|---|---|---|
| response_mode | No | Mode. | |
| transcript_id | Yes | ENST. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.7Input schema / properties / response_mode / defaultRemoved value: -"compact"Input schema / properties / response_mode / descriptionPrevious value: -"Verbosity: minimal|compact|standard|full (default compact)."New value: +"Mode."Input schema / properties / response_mode / typeRemoved value: -"string"Input schema / properties / transcript_id / descriptionPrevious value: -"A versioned Ensembl transcript id (the .N version suffix is required), e.g. ENST00000269305.4. Resolve a gene symbol with resolve_transcript first."New value: +"ENST."Input schema / properties / transcript_id / examplesPrevious value: -[
- "ENST00000269305.4"
-]New value: +[
+ "ENST00000269305.9"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "M": {
+ "additionalProperties": false,
+ "patternProperties": {
+ "^(tool|request_id|capabilities_version)$": {
+ "type": "string"
+ },
+ "^data_versions$": {
+ "additionalProperties": false,
+ "minProperties": 8,
+ "patternProperties": {
+ "^(assembly|gencode|uniprot|gnomad|clinvar|pfam|metadome_app|data_doi)$": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "^elapsed_ms$": {
+ "type": "integer"
+ },
+ "^next_commands$": {
+ "items": {
+ "additionalProperties": false,
+ "minProperties": 2,
+ "properties": {
+ "arguments": {
+ "propertyNames": {
+ "const": "transcript_id"
+ },
+ "type": "object"
+ },
+ "tool": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "^unsafe_for_clinical_use$": {
+ "const": true
+ }
+ },
+ "required": [
+ "tool",
+ "request_id",
+ "data_versions",
+ "unsafe_for_clinical_use"
+ ],
+ "type": "object"
+ }
+ },
+ "oneOf": [
+ {
+ "additionalProperties": false,
+ "patternProperties": {
+ "^(dropped_summary|job_id|transcript_id|eta_hint|cold_build_warning|recommended_citation)$": {
+ "type": "string"
+ },
+ "^_meta$": {
+ "$ref": "#/$defs/M"
+ },
+ "^poll_after_s$": {
+ "type": "number"
+ },
+ "^status$": {
+ "enum": [
+ "ready",
+ "processing"
+ ]
+ },
+ "^success$": {
+ "const": true
+ }
+ },
+ "required": [
+ "success",
+ "_meta",
+ "job_id",
+ "transcript_id",
+ "status",
+ "poll_after_s",
+ "eta_hint",
+ "cold_build_warning",
+ "recommended_citation"
+ ]
+ },
+ {
+ "additionalProperties": false,
+ "patternProperties": {
+ "^(message|recovery_action|field|hint)$": {
+ "type": "string"
+ },
+ "^_meta$": {
+ "$ref": "#/$defs/M"
+ },
+ "^allowed_values$": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "^error_code$": {
+ "enum": [
+ "invalid_input",
+ "not_found",
+ "ambiguous_query",
+ "upstream_unavailable",
+ "rate_limited",
+ "internal"
+ ]
+ },
+ "^retryable$": {
+ "type": "boolean"
+ },
+ "^success$": {
+ "const": false
+ }
+ },
+ "required": [
+ "success",
+ "_meta",
+ "error_code",
+ "message",
+ "retryable",
+ "recovery_action"
+ ]
+ }
+ ],
+ "type": "object"
+}v0.3.1Output schema / (root)Previous value: -{
- "additionalProperties": true,
- "properties": {
- "_meta": {
- "additionalProperties": true,
- "type": "object"
- },
- "candidates": {
- "type": "array"
- },
- "cold_build_warning": {
- "type": [
- "string",
- "null"
- ]
- },
- "data_versions": {
- "additionalProperties": true,
- "type": "object"
- },
- "error_code": {
- "type": "string"
- },
- "eta_hint": {
- "type": [
- "string",
- "null"
- ]
- },
- "field": {
- "type": "string"
- },
- "hint": {
- "type": "string"
- },
- "job_id": {
- "type": "string"
- },
- "message": {
- "type": "string"
- },
- "poll_after_s": {
- "type": [
- "number",
- "null"
- ]
- },
- "recommended_citation": {
- "type": "string"
- },
- "recovery_action": {
- "type": "string"
- },
- "retryable": {
- "type": "boolean"
- },
- "status": {
- "type": "string"
- },
- "success": {
- "type": "boolean"
- },
- "transcript_id": {
- "type": "string"
- }
- },
- "required": [
- "success"
- ],
- "type": "object"
-}New value: +nullv0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations indicate readOnlyHint: false, idempotent: true, destructive: false, but the description adds no behavioral details. It does not mention side effects, permissions, or response characteristics. The description neither contradicts nor enhances the annotations, so it fails to provide transparency beyond the minimal flags.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is not a sentence but a raw signature. It is extremely concise but fails to convey any meaningful content. The structure is purely syntactic, offering no explanatory value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The context is severely lacking. There is no explanation of the tool's function, the meaning of the parameters, the expected output, or any interaction with the system. The absence of an output schema and the bare signature make the tool completely opaque to an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides minimal descriptions: 'Mode.' for response_mode and 'ENST.' for transcript_id. These are uninformative. The tool description adds no additional meaning to the parameters, so the agent cannot infer what values are appropriate or what the parameters represent.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is only the function signature 'request_tolerance_landscape(transcript_id, response_mode=).' It does not state what the tool does, what resource it acts on, or any verb. It is a tautology restating the name, providing no purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus the sibling tools. No context, prerequisites, or conditions are given, leaving the agent without any decision-making information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.