Skip to main content
Glama

Get Gene Cross-References

get_gene_cross_references
Read-onlyIdempotent

Maps a gene symbol or HGNC ID to external database cross-references including NCBI, Ensembl, UniProt, RefSeq, and OMIM. Supports filtering by database and response verbosity.

Instructions

Return external database cross-references for a gene (forward identifier mapping): NCBI Gene, Ensembl, UniProt, RefSeq, MANE Select, OMIM, UCSC, VEGA, CCDS, MGI, RGD, Orphanet, COSMIC, PubMed. response_mode sets the default field set: minimal=NCBI+Ensembl ids; compact (default)=the high-value ids (NCBI, Ensembl, UniProt, RefSeq, MANE Select, OMIM, CCDS); standard/full=every populated field. databases optionally filters to specific sources by field key OR friendly label (e.g. 'mane', 'ncbi', 'uniprot') and OVERRIDES the response_mode tier; an unknown key is rejected with invalid_input + did-you-mean. Resolve the gene from an id/symbol/alias first. Signature: get_gene_cross_references(query, databases=, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesA gene symbol (current/previous/alias, case-insensitive) or HGNC id (HGNC:1100 or 1100).
databasesNoOptional database filter, e.g. ['ensembl','uniprot','omim'].
response_modeNoVerbosity: minimal | compact | standard | full (default compact).compact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
_metaNo
fieldNo
symbolNo
hgnc_idNo
messageNo
successNo
obsoleteNo
retryableNo
candidatesNo
error_codeNo
match_typeNo
replaced_byNo
allowed_valuesNo
database_countNo
recovery_actionNo
cross_referencesNo
Behavior4/5

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

Annotations declare the tool as read-only and idempotent. The description adds behavioral details: how response_mode affects output sets, that databases override the mode, and error behavior for unknown keys. This provides context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph with useful information, but it could be more structured with bullet points for modes and filter behavior. The 'Signature' line is redundant with the input schema.

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 complexity (multiple databases, response modes, filtering), the description covers usage, edge cases (invalid keys), and resolution steps. While an output schema exists, the description does not detail return format, but the provided details are sufficient for correct invocation.

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?

Schema coverage is 100%, but the description significantly augments it: for 'query' it clarifies accepted formats (symbol, HGNC id), for 'databases' it explains override behavior and error handling, for 'response_mode' it lists the field sets for each mode. This adds high value.

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 explicitly states 'Return external database cross-references for a gene (forward identifier mapping)' and lists many databases. It distinguishes from siblings like 'resolve_gene_by_xref' by specifying forward mapping and from 'get_gene' by focusing on cross-references.

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 advises 'Resolve the gene from an id/symbol/alias first' and explains when to use response modes and the databases filter, including error handling for invalid keys. However, it does not explicitly contrast with other tools like 'resolve_gene_by_xref'.

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/hgnc-link'

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