Skip to main content
Glama
Sign In
orphanet-link

orphanet-link

by berntpopp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Orphanet Diagnostics

get_diagnostics
Read-onlyIdempotent

Check Orphanet index freshness and runtime diagnostics: version, counts, build time, error/latency metrics, cache hit ratio. Use to confirm data freshness or diagnose data_unavailable errors.

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().

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "_meta": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "allowed_values": {
-      "type": "array"
-    },
-    "build": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "built_utc": {
-      "type": "string"
-    },
-    "candidates": {
-      "type": "array"
-    },
-    "data_available": {
-      "type": "boolean"
-    },
-    "error_code": {
-      "type": "string"
-    },
-    "field": {
-      "type": "string"
-    },
-    "hint": {
-      "type": "string"
-    },
-    "mapping_count": {
-      "type": "integer"
-    },
-    "message": {
-      "type": "string"
-    },
-    "obsolete_count": {
-      "type": "integer"
-    },
-    "orphanet_version": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "recovery_action": {
-      "type": "string"
-    },
-    "retryable": {
-      "type": "boolean"
-    },
-    "runtime": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "schema_version": {
-      "type": "integer"
-    },
-    "success": {
-      "type": "boolean"
-    },
-    "term_count": {
-      "type": "integer"
-    },
-    "xref_count": {
-      "type": "integer"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate readOnly, openWorld, idempotent, non-destructive. The description adds detailed behavioral context (response includes runtime metrics, cache hit/miss, over-fetch detection) and confirms no parameters.

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 front-loaded with purpose and includes a signature. It is informative but slightly verbose with detailed runtime metrics. Overall 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 no output schema, the description fully explains the return content (status report with metrics). It covers what the tool does, why to use it, and what to expect, making it complete for agent invocation.

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 exist and schema coverage is 100%. The description implicitly confirms this by stating 'Signature: get_diagnostics()'. No additional parameter details needed.

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 the tool reports Orphanet index status with specific metrics (freshness, version, counts, runtime). It distinguishes from siblings by focusing on system diagnostics rather than disease data.

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

Usage Guidelines4/5

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

The description explicitly says 'Use this to confirm freshness or diagnose a data_unavailable error'. It provides clear context for when to use, though it doesn't explicitly state when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools