Skip to main content
Glama
berntpopp
by berntpopp

Resolve Cross-Reference

resolve_xref
Read-onlyIdempotent

Resolve an external disease identifier (OMIM, MONDO, ICD-10, etc.) to the Orphanet disorder(s) that map to it. Returns matching Orphanet terms with pagination support.

Instructions

Resolve an external cross-reference CURIE (OMIM/MONDO/ICD-10/ICD-11/UMLS/GARD/MeSH/MedDRA) back to the Orphanet disorder(s) that map to it. Returns matches[] plus a pagination block {total, returned, limit, offset, truncated, next_offset}; when truncated, next_commands carries a forward-page step. Miss semantics (list-shaped, unlike resolve_disease): a malformed CURIE is rejected with invalid_input, while a well-formed but unmapped CURIE returns an empty page (total: 0), not not_found. Signature: resolve_xref(xref_id, limit=, offset=, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax matches (default 50).
offsetNoRows to skip for forward paging (default 0).
xref_idYesAn external cross-reference CURIE (prefix:local), e.g. OMIM/MONDO/ICD-10, to resolve back to the Orphanet term(s) that map to it.
response_modeNoVerbosity: minimal|compact|standard|full (default compact).compact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
_metaNo
fieldNo
limitNo
totalNo
offsetNo
prefixNo
matchesNo
messageNo
successNo
xref_idNo
returnedNo
retryableNo
truncatedNo
candidatesNo
error_codeNo
normalizedNo
next_offsetNo
allowed_valuesNo
recovery_actionNo
Behavior5/5

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

Beyond annotations (readOnly, openWorld, idempotent, non-destructive), the description details pagination behavior (truncated, next_commands, next_offset), miss semantics (invalid_input vs empty page), and the signature. This adds significant behavioral context.

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 with front-loaded main purpose, followed by pagination details, miss semantics, and signature. Every sentence adds value; it's moderately concise but not overly verbose.

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?

Given the tool's complexity (4 params, output schema exists), the description covers purpose, pagination, error handling, parameter behavior, and signature. It is complete and informative enough for an AI agent to select and invoke 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 baseline is 3. The description adds value by explaining response_mode verbosity levels, the pagination context for limit and offset, and the CURIE format for xref_id. This goes beyond the schema descriptions.

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 defines the tool's purpose: resolving external cross-reference CURIEs back to Orphanet disorders. It lists supported prefix sources and explicitly distinguishes from resolve_disease by noting the different miss semantics.

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 explains when to use the tool (resolve a cross-reference CURIE) and contrasts with resolve_disease using list-shaped semantics. It also covers error handling for malformed vs unmapped CURIEs, providing good usage context, though it doesn't explicitly exclude scenarios for sibling tools like search_diseases.

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

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