Skip to main content
Glama
berntpopp
by berntpopp

Get Disease Classification

get_disease_classification
Read-onlyIdempotent

Retrieve the immediate parent and child Orphanet classifications for a given rare disease, using ORPHAcode, label, or external reference.

Instructions

Return the immediate Orphanet classification parents and children for a disorder. Use get_disease_ancestors / get_disease_descendants for the transitive closure. Signature: get_disease_classification(term, 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.
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
candidatesNo
orpha_codeNo
nameNo
parentsNo
childrenNo
Behavior4/5

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

Annotations already declare safe read operation and idempotency. Description adds useful context about immediate vs transitive classification, which is not in 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?

Two concise sentences, front-loaded with purpose, then usage guidance. No wasted words.

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 rich annotations, full schema coverage, and output schema, the description is complete. It specifies what is returned (immediate parents/children) and when to use alternatives.

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

Parameters3/5

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

Schema covers all parameters fully (100% coverage). Description briefly mentions them in signature but adds no new meaning 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?

Description clearly states the tool returns immediate Orphanet classification parents and children, and distinguishes from siblings that handle transitive closure.

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

Usage Guidelines5/5

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

Explicitly instructs to use get_disease_ancestors/get_disease_descendants for transitive closure, providing clear when-to-use guidance and alternatives.

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