Skip to main content
Glama
berntpopp
by berntpopp

Get Disease

get_disease
Read-onlyIdempotent

Retrieve detailed rare disease records from Orphanet by ORPHAcode, name, or external identifier to obtain definition, synonyms, cross-references, classification, age of onset, inheritance, and disorder type.

Instructions

Return an Orphanet disease record: definition, synonyms, grouped cross-references, classification parents/children, age of onset, inheritance, and disorder type. The term accepts an ORPHAcode, a label/synonym, or an external xref CURIE (resolved first). Pass fields=['xrefs.OMIM', ...] for a sparse projection. Signature: get_disease(term, response_mode=, fields=).

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.
response_modeNoVerbosity: minimal|compact|standard|full (default compact).compact
fieldsNoSparse fieldset: return ONLY these top-level keys (dot into a grouped object, e.g. 'xrefs.OMIM'). Identity anchors (orpha_code, name, orphanet_version) are always included. Omit for the full payload.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNo
_metaNo
error_codeNo
messageNo
retryableNo
recovery_actionNo
fieldNo
allowed_valuesNo
hintNo
candidatesNo
orpha_codeNo
nameNo
definitionNo
synonymsNo
xrefsNo
parentsNo
childrenNo
top_groupingsNo
subsetsNo
obsoleteNo
match_typeNo
orphanet_versionNo
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true. The description adds useful behavioral context: term resolution order (xref resolved first), sparse projection semantics, and identity anchors always included. No contradictions.

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?

Two sentences plus a signature line. Information-dense but clearly organized. Could be slightly more structured (e.g., separate sections), but very efficient.

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 3 parameters and existing output schema, the description covers all necessary information: return content, term formats, field filtering, and response verbosity. No gaps identified for a single-record retrieval tool.

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 beyond the schema by explaining term types with examples, summarizing the response_mode enum, and detailing the fields dot-notation for sparse projections. The signature line provides a quick parameter summary.

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 returns an Orphanet disease record with specific fields (definition, synonyms, cross-references, etc.). It distinguishes from sibling tools like search_diseases and find_diseases_by_*, which serve different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the term input formats (ORPHAcode, label, xref) and optional field projection, but does not explicitly state when to use this tool vs. alternatives like search_diseases or get_disease_genes. The context is implied but not explicit.

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