Skip to main content
Glama

can-immune

by io.github.sanjaysgk
OverviewDiscussionsAdmin

get_gene_mutations

List individual mutations in a gene (a bounded sample of rows).

Each row gives the CAN-IMMUNE mutation ID (CANLIB...), the amino-acid change, the
CDS change, mutation type (missense / complex substitution), data source, the
sample it came from, its primary site, and the mutant peptide. Ordered by mutation
ID. Capped at `limit` rows (max 100) for speed - for the complete table of a
heavily-mutated gene, link the user to the gene page on the website.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geneYesExact gene symbol whose mutations you want, e.g. 'TP53'.
limitNoMax mutation rows to return (1-100). Default 50. This is a bounded sample, not the full list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the burden. It discloses that results are capped at limit (max 100), ordered by mutation ID, and lists every column returned. This goes beyond a simple read operation and gives the agent clear expectations for performance and output structure.

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?

The description is two concise paragraphs. The first sentence is a crisp purpose statement, and the second paragraph efficiently enumerates the fields. There is no fluff; every sentence serves a distinct role in explaining the tool's behavior.

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?

For a simple list tool with 2 parameters and no output schema, the description covers purpose, row schema, ordering, limit behavior, and provides a fallback for complete data. It is sufficiently complete for an agent to invoke and interpret results without ambiguity.

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% for both parameters. The description adds context beyond the schema by explaining that limit caps the output as a 'bounded sample' and exists for speed, which helps the agent reason about trade-offs. This is a modest but meaningful enhancement over the schema alone.

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 opens with 'List individual mutations in a gene', which is a specific verb+resource+scope statement that clearly differentiates from sibling tools like get_gene or search. It also details the exact row contents, making the purpose unmistakable.

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?

It clearly states this tool returns a bounded sample, and for a complete table of a heavily-mutated gene, directs users to the gene page on the website. While it doesn't name sibling tools like get_gene, the alternative for the full dataset is explicit, giving good when-to-use and when-not-to-use context.

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

All can-immune toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources