apibase

Get Comprehensive Gene Details

mygene.genes.info

Read-onlyIdempotent

Retrieve comprehensive annotation data for a single gene by its NCBI Entrez Gene ID or Ensembl gene ID. Returns the full gene record including: official symbol and name, gene type (protein-coding, ncRNA, pseudo, etc.), species taxon, gene summary, Ensembl transcript and protein IDs, UniProt Swiss-Prot accession, gene aliases, genomic coordinates (chromosome, start, end, strand), KEGG and Reactome pathway memberships, and Gene Ontology (GO) annotations across biological process, cellular component, and molecular function. Use mygene.genes.search or mygene.genes.symbol to discover Entrez Gene IDs first.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fields`	No	Comma-separated fields to return. Default includes: symbol, name, taxid, entrezgene, type_of_gene, summary, ensembl, uniprot, alias, genomic_pos, pathway. Use "all" to fetch every available annotation (includes GO terms, RefSeq, PDB, OMIM, etc.).
`gene_id`	Yes	Gene identifier — NCBI Entrez Gene ID (e.g. "1017" for CDK2, "672" for BRCA1) or Ensembl gene ID (e.g. "ENSG00000123374"). Obtain Entrez Gene IDs from mygene.search or mygene.query_by_symbol results.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No	Present only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
`result`	No	Tool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, read-only operation. The description adds detail about the output contents but doesn't disclose behavioral aspects beyond what annotations cover, such as potential rate limits or error conditions. Given annotations, the description's contribution is limited but not contradictory.

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 description is well-structured, starting with the action, then the input, then a detailed list of returned data, and finally usage guidance. While it is relatively long, every sentence adds useful information without redundancy. The format is logical and easy to parse.

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?

Given the tool's moderate complexity (2 parameters, 1 required) and the presence of an output schema, the description is sufficiently complete. It covers the input formats, return fields, and how to obtain IDs. It does not mention edge cases or limitations, but the output schema likely covers return structure. Overall, it provides enough context for an agent to use the tool correctly.

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 both parameters are documented. The description adds value by explaining the 'fields' parameter's default values and the meaning of 'all', and provides concrete examples for gene_id (e.g., '1017' for CDK2). These examples and explanations go beyond the schema's basic descriptions, improving usability.

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 the tool's purpose: retrieving comprehensive annotation data for a single gene by NCBI Entrez or Ensembl ID. It enumerates specific data fields returned (symbol, name, gene type, coordinates, pathways, GO annotations), making it unambiguous. It also distinguishes itself from sibling tools by explicitly recommending mygene.genes.search or mygene.genes.symbol for ID discovery.

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?

The description provides explicit guidance on when to use this tool: when you already have a gene ID, and it tells you to use search or symbol tools to discover IDs first. It doesn't mention the mygene.genes.batch sibling for handling multiple genes, but the single-gene focus is clear. The guidance is practical and actionable, though not exhaustive.

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

All apibase tools Inspect

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.