Skip to main content
Glama
berntpopp
by berntpopp

Get Diseases (batch)

get_disease_batch
Read-onlyIdempotent

Retrieve up to 50 rare disease records in one batch request using ORPHAcodes, labels, or cross-references, with options for sparse projections and verbosity levels.

Instructions

Fetch many disease records in one call (partial success per item: each row is the record or its own ok=false/error_code/message). Each term accepts an ORPHAcode, label, or xref CURIE; pass fields=[...] for a sparse projection. Max 50 items; compact per item. Signature: get_disease_batch(terms, response_mode=, fields=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termsYes1..50 ids/labels/xrefs.
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
countNo
resultsNo
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds significant behavioral detail: partial success per item, accepted identifier types (ORPHAcode, label, xref CURIE), sparse projection via fields, max 50 items, and compact format. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the key purpose. Every sentence contributes meaningful information without redundancy or fluff.

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 presence of an output schema (not shown) and the description covering partial success, identifiers, limits, and projection, it is fairly complete. It could mention the response is an array, but the behavioral description suffices.

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 clarifying that 'terms' accepts ORPHAcodes, labels, or xref CURIES, and provides a signature line showing parameter order. For fields, it reinforces sparse projection with examples. This exceeds 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 clearly states 'Fetch many disease records in one call', using a specific verb and resource. It distinguishes from sibling tools like get_disease (single record) and search_diseases by emphasizing batch retrieval and partial success.

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 implies usage for batch retrieval of multiple disease records, but does not explicitly state when not to use it or mention alternatives. It provides a max limit of 50 items but lacks direct comparison with siblings.

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