Skip to main content
Glama

can-immune

by io.github.sanjaysgk
OverviewDiscussionsAdmin

get_gene

Get the full profile for one gene by exact symbol.

Returns total mutations and how they split between cell lines vs tissues, unique
mutant peptides, sample and transcript counts, UniProt accession / name / reviewed
status, the top ~15 recurrent mutations in that gene, and a link to the gene page.
Use this after `search_genes` (or when you already know the symbol) to answer
detailed questions about a single gene. Returns an error field if the symbol is
not found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesExact HGNC gene symbol, e.g. 'TP53', 'KRAS', 'EGFR'. Use search_genes first if unsure of the exact symbol.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It fully discloses the return contents and explicitly mentions that an error field is returned if the symbol is not found. It does not explicitly state read-only behavior, but 'Get' makes this evident; the error-handling disclosure is a strong positive.

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 compact yet information-dense: purpose first, then return summary, then usage context, then error behavior. Every sentence adds unique value; no word is wasted.

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 tool's simplicity (1 parameter, no output schema, no annotations), the description covers everything needed: what it returns, error behavior, and when to use it. It fully compensates for missing structured metadata.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The parameter description provides concrete meaning beyond the schema: 'Exact HGNC gene symbol' with examples and a note to use search_genes first if unsure. Schema coverage is 100%, and the description enriches the single parameter with practical guidance.

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 begins with 'Get the full profile for one gene by exact symbol' — a specific verb+resource that clearly states the action. It also enumerates the returned data fields, distinguishing it from sibling tools like get_gene_mutations and search_genes.

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 instructs to use after search_genes or when the symbol is already known, and says it answers detailed questions about a single gene. This clearly establishes when this tool is appropriate and names the alternative for symbol lookup.

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