Minos Health

Browse a classification

browse_codes

Read-onlyIdempotent

List one level of ICD-10 PL, ICD-9 PL or ICD-11 PL: the chapters when parent and node are omitted, else the children of parent or of a node id from an earlier listing (ICD-11 blocks have a node id, no code). Levels stop at 400 entries with truncated=true. Use search_codes for words, get_code for one code's details.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "system": "<system>"
    },
    "name": "browse_codes"
  }
}

Input Schema

Name	Required	Description
`node`	No	Node id from an earlier listing, for ICD-11 blocks without a code.
`parent`	No	Code whose children to list.
`system`	Yes	Classification of the code.

Output Schema

Name	Required	Description	Default
`notice`	Yes
`parent`	Yes
`system`	Yes
`children`	Yes
`truncated`	Yes
`release_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description does not need to re-state safety. It adds meaningful behavior beyond annotations: listings are capped at 400 entries with truncated=true, and ICD-11 block nodes are identified by node id rather than code. Ordering and error behavior are not described, but they are minor omissions for this read-only listing tool.

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?

The description is compact and front-loaded: hierarchy behavior first, truncation limit second, sibling alternatives last. Every sentence carries operational information with no repetition of schema or annotation details.

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 the rich input schema, full description coverage, annotations, and an output schema, the description supplies everything an agent needs to choose the tool and invoke it correctly. Return-format details are appropriately left to the output schema.

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 the baseline is 3. The description adds semantic meaning beyond the schema by explaining that omitting both parent and node returns chapters, while supplying either returns children, and by clarifying the node id case for ICD-11 blocks.

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 states a specific verb ('List one level') and resource (ICD-10 PL, ICD-9 PL, ICD-11 PL), and explicitly distinguishes this hierarchy-browsing tool from search_codes and get_code. An agent can identify its purpose without opening the schema.

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?

It gives explicit routing rules: omit parent and node to get chapters; supply parent or node to get children. It also names the alternatives and when to use them: search_codes for words and get_code for one code's details.

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

All Minos Health tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.