Skip to main content
Glama

Get Mutation Position Counts

get_mutation_position_counts
Read-only

Count portal-wide mutations at specific protein positions of a gene across public cBioPortal studies to check recurrence without denominators; use the frequency tool for rates.

Instructions

Get portal-wide mutation counts at protein positions of a gene (e.g. BRAF 600) across all public cBioPortal studies: a recurrence check with no denominator (overlapping cohorts count repeatedly; restricted studies included). For a frequency use get_gene_alteration_frequency. Signature: get_mutation_position_counts(gene, positions).

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>",
      "positions": "<positions>"
    },
    "name": "get_mutation_position_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYesGene symbol (HGNC, e.g. BRAF) or NCBI Gene ID (673 or NCBIGene:673).
positionsYesProtein positions (1-20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower. The description still adds real behavioral context beyond them: counts are aggregated across all public studies with no denominator, cohorts overlap and are counted repeatedly, and restricted studies are included. The only notable gap is the shape of the returned result, which is neither in the description nor an output schema.

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 caveats and the alternative are front-loaded ahead of any detail, and every sentence carries information. The trailing 'Signature: get_mutation_position_counts(gene, positions)' largely restates the required parameters already in the schema, which is minor waste.

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?

For a two-parameter read tool with no output schema, the definition covers scope, data provenance caveats, and the sibling alternative. What an agent cannot learn is the return structure (per-position counts, ordering, empty positions), which matters slightly more here because no output schema exists.

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%, so both parameters are already documented with types, bounds, and examples. The description adds only an illustrative usage ('BRAF 600') and does not elaborate on position semantics (e.g. residue numbering or how multiple positions are keyed in the response). 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?

States a specific verb and resource (get mutation counts at protein positions of a gene), pins the scope (portal-wide, all public cBioPortal studies), and gives a concrete example (BRAF 600). It also names the sibling it is not (get_gene_alteration_frequency), so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this for a recurrence check with no denominator, and use get_gene_alteration_frequency when a frequency is wanted. It additionally names the conditions that make the numbers what they are (overlapping cohorts count repeatedly, restricted studies are included), which is exactly the guidance an agent needs to pick correctly and interpret the result.

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