Skip to main content
Glama

Get Mutation Hotspots

get_mutation_hotspots
Read-only

Fetch Cancer Hotspots for a gene: residue types, tumor counts, q-values, and variants per residue. Check if a change like V600E is a hotspot and get its variant tumor count.

Instructions

Get Cancer Hotspots calls for a gene (bundled v2 + 3D snapshot, ODbL 1.0): residue, type (single_residue, in_frame_indel, splice_site, 3d), tumor_count, q_value (3d: p_value, clusters), variants and tumor_types per residue. With residue (V600, V600E, R175H) it answers is_hotspot and, for a change, variant_tumor_count. Residues follow the assembly's transcript (default GRCh38). Signature: get_mutation_hotspots(gene, residue=, assembly=).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gene": "<gene>"
    },
    "name": "get_mutation_hotspots"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYesGene symbol (HGNC, e.g. BRAF) or NCBI Gene ID (673 or NCBIGene:673).
residueNoResidue or change: V600 or V600E.
assemblyNoBuild whose transcript numbers the residues (default GRCh38).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description still adds real value by naming the data provenance (bundled v2 + 3D snapshot), the ODbL 1.0 license, and the field semantics of the payload. It stops short of covering error behavior (unknown gene), whether 3D records are always present, or result size/pagination, which matters for an open-world read.

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

Conciseness3/5

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

Purpose is front-loaded, but the body is two dense run-on sentences thick with parentheticals and abbreviations ('bundled v2 + 3D snapshot, ODbL 1.0', '3d: p_value, clusters'). The trailing 'Signature: get_mutation_hotspots(gene, residue=, assembly=)' merely restates the schema and does not earn its place.

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?

With no output schema, the description correctly takes on the burden of describing the return fields and does so field by field, including the 3D variant fields. For a 3-parameter read tool it is close to sufficient; only failure modes and result volume are unaddressed.

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 the baseline is 3, and the description earns above it by clarifying that `residue` accepts either a position (V600) or a change (V600E, R175H) and that the distinction changes the returned fields, plus restating the GRCh38 default for `assembly`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact dataset ('Cancer Hotspots') and resource (a gene), and enumerates the fields returned (residue, type, tumor_count, q_value, variants, tumor_types). That is specific enough to distinguish it from a plain mutation-list sibling, though no sibling is named explicitly.

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?

It explains that supplying `residue` switches the answer to `is_hotspot` and `variant_tumor_count`, which implies when to pass that parameter. It never states when to prefer a different tool (e.g. get_gene_mutations) or what happens with gene-only calls, leaving usage only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.