Skip to main content
Glama
berntpopp
by berntpopp

Map Cross-Ontology

map_cross_ontology
Read-onlyIdempotent

Retrieve cross-references from an Orphanet disorder to external ontologies (OMIM, MONDO, ICD-10, etc.) with mapping relations. Optionally filter by source prefixes.

Instructions

List an Orphanet disorder's cross-references to other ontologies, grouped by source (OMIM/MONDO/ICD-10/ICD-11/UMLS/GARD/MeSH/MedDRA), each with its mapping relation. Optionally restrict to a subset of sources, or pass fields=['xrefs.OMIM'] for a sparse projection. count is the number of leaf mapping rows (individual targets), not the number of source groups. Signature: map_cross_ontology(term, prefixes=, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesAn ORPHAcode (ORPHA:166024 or 166024), a disease label/synonym, or an external xref CURIE that resolves to a single Orphanet term.
prefixesNoRestrict to these source prefixes, e.g. ['OMIM', 'MONDO'].
response_modeNoVerbosity: minimal|compact|standard|full (default compact).compact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
nameNo
_metaNo
countNo
fieldNo
messageNo
successNo
mappingsNo
retryableNo
candidatesNo
error_codeNo
orpha_codeNo
allowed_valuesNo
prefixes_filterNo
recovery_actionNo
orphanet_versionNo
Behavior4/5

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

Annotations already indicate safe, idempotent, non-destructive behavior. The description adds behavioral details like grouping by source, mapping relation, and count semantics, which go beyond the annotations.

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 moderately concise (3 lines) and front-loaded with core purpose. Each sentence adds value, though it could be slightly more streamlined.

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 complexity of cross-ontology mapping with multiple sources, response modes, and an existing output schema, the description covers all essential aspects: parameters, behavior, and examples, making it sufficient for correct tool invocation.

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% providing baseline 3. The description adds extra context: explains 'count' meaning, gives signature examples, and clarifies that prefixes restrict sources, improving parameter understanding.

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 verb 'List' and the resource 'cross-references to other ontologies', specifying grouping by source and mapping relation. It distinguishes from sibling tools like get_disease_genes which list genes, not 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?

It explains optional parameters for restricting sources and sparse projection, and clarifies the meaning of 'count'. It does not explicitly state when not to use this tool, but the context implies it is for cross-ontology lookups.

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