Skip to main content
Glama

Get Marker Alleles & Mutations

get_marker_alleles
Read-onlyIdempotent

Retrieve all phenotypic alleles and mutations for a mouse gene, including allele details and generation-method counts. Filter by allele type to focus on specific mutations.

Instructions

Return the phenotypic alleles / mutations for a mouse marker — the gene page's 'All Mutations and Alleles' panel. Includes per-allele {allele_id, symbol, name, allele_type, attributes, pubmed_ids} and the generation-method category_counts (Targeted, Endonuclease-mediated, Radiation induced, Chemically induced, Transgenic, ...). allele_type optionally filters (accepts friendly tokens like 'knockout', 'crispr', 'targeted'). Returns a truncation contract {total, returned, limit, truncated}; when truncated, next_commands includes a widen step. Signature: get_marker_alleles(query, allele_type=, limit=, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesA mouse marker symbol (current or synonym, case-insensitive), an MGI id (MGI:98968 or 98968), or a human gene symbol / HGNC id for the ortholog.
allele_typeNoOptional allele-type filter (e.g. 'Targeted', 'knockout', 'crispr').
limitNoMax alleles returned (default 200).
response_modeNoVerbosity: minimal | compact | standard | full (default compact).compact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNo
_metaNo
error_codeNo
messageNo
retryableNo
recovery_actionNo
fieldNo
allowed_valuesNo
hintNo
candidatesNo
mgi_idNo
symbolNo
allele_type_filterNo
total_allelesNo
category_countsNo
totalNo
returnedNo
limitNo
truncatedNo
allelesNo
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but description adds truncation behavior, next_commands with widen step, and response mode details, which are beyond what annotations provide.

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?

Front-loaded purpose, but includes a somewhat verbose list of output fields and category counts. Still efficient overall with a clear signature line.

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?

Output schema exists, so return values need not be fully described. Description covers input parameters, truncation contract, and next_commands, making it complete for a tool of this complexity.

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 baseline is 3. Description adds value by mentioning friendly tokens for allele_type (e.g., 'knockout', 'crispr') and providing a signature summary.

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 clearly states it returns phenotypic alleles/mutations for a mouse marker, using specific verbs and resource. It references the 'All Mutations and Alleles' panel, distinguishing it from sibling tools like get_marker or search_markers.

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?

The description implies usage by referencing the gene page's panel, but lacks explicit guidance on when to use vs alternatives. No exclusions or comparisons to sibling tools are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/berntpopp/mgi-link'

If you have feedback or need assistance with the MCP directory API, please join our Discord server