Skip to main content
Glama
berntpopp
by berntpopp

Get Protein Cross-References

get_protein_cross_references
Read-onlyIdempotent

Fetch database cross-references (PDB, Ensembl, RefSeq, etc.) for a UniProt accession. Optionally limit to specific databases; returns grouped references with short IDs or full IRIs.

Instructions

Return database cross-references for an entry, grouped by database (PDB, AlphaFoldDB, Ensembl, RefSeq, Reactome, STRING, InterPro, ...). Optionally restrict to specific databases (case-sensitive); any requested name that matched nothing is echoed under unmatched_databases with a did-you-mean, so a typo never reads as 'no data'. response_mode (default compact) returns short ids; full restores raw IRIs. Returns every cross-reference database; use map_identifiers for a focused primary-id mapping. Signature: get_protein_cross_references(accession, databases=, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accessionYesUniProtKB accession, e.g. P05067 (isoforms like P05067-2 accepted).
databasesNoDatabase short names to keep (omit for all).
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
accessionNo
database_countNo
totalNo
countsNo
by_databaseNo
truncated_databasesNo
requested_databasesNo
unmatched_databasesNo
database_hintNo
Behavior5/5

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

Beyond annotations (readOnly, idempotent), description adds grouping by database, case-sensitive filtering, unmatched databases echoed with did-you-mean, and response mode effects. No contradiction with annotations.

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?

Three sentences plus signature, no waste. Purpose front-loaded. Every sentence adds value.

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?

With output schema present, description completes the picture: explains all parameters, behavior, and sibling differentiation. No gaps.

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%, baseline 3. Description adds meaning: explains response_mode returns short ids vs full IRIs, and databases parameter case-sensitivity with typo handling. Accession example given. Adds value beyond 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?

Clearly states 'Return database cross-references for an entry, grouped by database', specifying verb and resource. Distinguishes from sibling 'map_identifiers' by directing focused mapping elsewhere.

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?

Provides context on optional restriction to specific databases with case-sensitivity and typo handling. Contrasts with map_identifiers for focused mapping. Could be more explicit about when not to use, but sufficient.

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

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