Minos Health

Code details

get_code

Read-onlyIdempotent

Get one ICD-10 PL, ICD-9 PL or ICD-11 PL code as its page shows it: title, hierarchy, children, notes, attributes, ICD-9 rank, WHO map rows and, for ICD-10 and ICD-9, the JGP groups whose attachment 9 lists name it on service_date. Find the code with search_codes first; open a listed group with get_jgp_group.

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>",
      "code": "<code>"
    },
    "name": "get_code"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	The code as printed, e.g. J18.9, 53.03 or BA00.
`system`	Yes	Classification of the code.
`service_date`	No	Day of care, YYYY-MM-DD; picks the release in force. Default today in Poland.

Output Schema

Name	Required	Description	Default
`code`	Yes
`path`	Yes
`notes`	Yes
`title`	Yes
`notice`	Yes
`system`	Yes
`release`	Yes
`children`	Yes
`jgp_lists`	No
`attributes`	Yes
`who_map_rows`	No
`procedure_rank`	No
`children_truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.5/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, closed-world behavior. The description adds useful scope detail beyond annotations, notably that service_date selects the release in force and that JGP group attachment is limited to ICD-10 and ICD-9.

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 sentences, front-loaded with the core action and followed by workflow routing. The detail list is dense but every clause identifies actual output or behavior.

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 an output schema and rich annotations, the description provides everything needed to invoke the tool correctly: supported systems, code input, optional service_date behavior, and the surrounding search/group workflow.

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 still adds meaning: it clarifies that the code is treated as printed on its page and explains the service_date role in selecting the applicable release and JGP group attachment.

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 and resource: retrieves a single ICD-10 PL, ICD-9 PL or ICD-11 PL code with the full detail set shown on its page. It also enumerates the returned sections, making it clearly distinct from search_codes and browse_codes.

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?

It gives explicit sequencing guidance: use search_codes to find the code first, and use get_jgp_group to open a listed group. It does not explicitly state when not to use this tool versus browse_codes, so it falls short of a full 5.

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.