Skip to main content
Glama
berntpopp
by berntpopp

Get Disease

get_disease
Read-onlyIdempotent

Retrieve a disease record from Orphanet using an ORPHAcode, disease label, or external reference. Returns definition, synonyms, cross-references, classification, and optional gene or phenotype data.

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). xrefs are grouped by source; any nested count is leaf rows, not groups. Pass fields=['xrefs.OMIM', ...] for a sparse projection, or include=['genes','phenotypes','prevalence','disability'] to compose a full entity in ONE call. Signature: get_disease(term, response_mode=, fields=, include=).

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.
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.
includeNoCompose extra association sections into the single record (any of: genes, phenotypes, prevalence, disability) so a full entity needs one call instead of a per-section fan-out. Omit for the base record only.
response_modeNoVerbosity: minimal|compact|standard|full (default compact).compact

Output Schema

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

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

Annotations declare safe read-only operations. The description adds behavior details: xref resolution order, grouping, count meaning, and response_mode verbosity levels, providing context beyond 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 information-dense but well-structured with purpose first, then parameter details, then signature. Some brevity could be improved, but it is not excessively wordy.

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 the tool's complexity and presence of an output schema, the description covers key aspects. It could mention more about when to use sibling tools, but overall it is sufficiently complete.

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

Parameters5/5

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

Schema coverage is 100%; the description adds significant value by explaining field dot-notation, include composition, term format options, and provides examples and a signature, exceeding baseline.

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 specifies the tool returns an Orphanet disease record with definition, synonyms, cross-references, classification, and more. It clearly distinguishes from sibling tools that return lists or specific sections (e.g., get_disease_genes).

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 accepted term types and the include parameter for full entity retrieval, but does not explicitly state when not to use this tool or contrast with alternatives like get_disease_genes or get_disease_phenotypes.

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