Skip to main content
Glama
berntpopp
by berntpopp

Get Orphanet Diagnostics

get_diagnostics
Read-onlyIdempotent

Confirm data freshness or diagnose data_unavailable errors by inspecting local Orphanet index status, including build details, request/error counts, latency percentiles, and cache metrics.

Instructions

Report the local Orphanet index status: whether the data is built, the loaded Orphanet release version, disorder counts, schema version, and when it was built, plus a runtime block (request/error counts, latency percentiles p50/p95/p99, a response_mode distribution that surfaces over-fetch, and a version-hash cache hit/miss ratio). Use this to confirm freshness or diagnose a data_unavailable error. Signature: get_diagnostics().

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
_metaNo
buildNo
fieldNo
messageNo
runtimeNo
successNo
built_utcNo
retryableNo
candidatesNo
error_codeNo
term_countNo
xref_countNo
mapping_countNo
allowed_valuesNo
data_availableNo
obsolete_countNo
schema_versionNo
recovery_actionNo
orphanet_versionNo
Behavior4/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds value by detailing the runtime block metrics and the signature, enhancing transparency 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.

Conciseness5/5

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

Single sentence with a usage note and signature. Extremely concise, no wasted words, front-loaded with key information.

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?

Fully complete given no parameters, comprehensive annotations, and existing output schema. Description covers all necessary context for a diagnostic 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?

No parameters; schema coverage is 100%. Description correctly omits parameter details, and the baseline of 4 applies due to zero parameters.

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?

Clearly states the tool reports the local Orphanet index status with specific metrics like build status, version, counts, and runtime diagnostics. Distinguishes from sibling tools that focus on diseases, genes, or phenotypes.

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 states 'Use this to confirm freshness or diagnose a data_unavailable error,' providing clear context for when to invoke this tool.

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