Skip to main content
Glama

Resolve Gene by Cross-Reference

resolve_gene_by_xref
Read-onlyIdempotent

Reverse identifier mapping: given an external database ID (e.g., Ensembl, RefSeq, UniProt), return the corresponding HGNC gene symbol. Supports version suffixes and cross-references.

Instructions

Reverse identifier mapping: find the HGNC gene(s) for an external database id. source is the database (entrez_id/ncbi, ensembl_gene_id, uniprot, refseq, mane_select, omim, ucsc, vega, ccds, mgi, rgd) and value is the id (e.g. source='ensembl_gene_id', value='ENSG00000157764'). A version suffix is tolerated (ENSG00000012048.23 resolves like ENSG00000012048), and a MANE Select transcript (ENST…/NM_…) resolves back to its gene. Signature: resolve_gene_by_xref(source, value, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesThe external identifier value to look up (a version suffix is fine).
sourceYesCross-reference database. Canonical keys: entrez_id, ensembl_gene_id, uniprot_ids, refseq_accession, mane_select, omim_id, ucsc_id, vega_id, ccds_id, ena, mgd_id, rgd_id. Common synonyms (ncbi, ensembl, uniprot, refseq, mane, omim, mgi, rgd) are also accepted.
response_modeNoVerbosity: minimal | compact | standard | full (default compact).compact
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and not destructive. The description adds behavioral context about version suffix handling and transcript resolution, which goes beyond annotations without contradiction.

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?

Two concise sentences plus a signature line. Every sentence is purposeful, no redundancy. The core purpose is front-loaded.

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 no output schema, the description does not explain return format, but for a lookup tool with annotations, the input guidance is sufficient. Missing mention of multiple/no results is minor.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description adds examples and explains source synonyms and version suffix handling, providing minor added value over the schema.

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 is a 'reverse identifier mapping' to 'find the HGNC gene(s) for an external database id', specifying verb and resource. It distinguishes from siblings like resolve_symbol (resolves symbols) and get_gene_cross_references (retrieves existing xrefs).

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 clear usage context with examples of source and value, tolerates version suffixes and MANE Select transcripts. It implicitly differentiates from alternatives but lacks explicit when-not-to-use statements.

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