Skip to main content
Glama

lookup_icd10_cm

Read-onlyIdempotent

Look up ICD-10-CM diagnosis codes with English and Chinese descriptions, category, and associated specialties. Search by code or keyword to find canonical names and explore related procedures.

Instructions

Look up ICD-10-CM diagnosis codes with English / Traditional Chinese descriptions, category, and the OPDSTAR specialties each code is keyed against. Use when the agent encounters an ICD-10 code in a note, claim, or rejection notice and needs the canonical name, or wants to free-text search by EN / 中文 keyword to find candidate codes. Typical follow-up: chain into get_procedures_for_icd({icd10, specialty}) to find the procedures commonly paired with the code, or check_icd_for_major_illness_eligibility({icd10}) to check 重大傷病 coverage. Scope note: Currently backed by OPDSTAR's specialty-keyed Taiwan-relevant subset (~3,000 codes covering the diagnoses doctors actually code on outpatient claims); the full CMS public-domain ICD-10-CM 2025 set (~70K codes) will be merged in a later release. Out of scope: SNOMED CT cross-mapping, international procedure codes (ICD-10-PCS), drug interactions. Reference only — clinical coding decisions require physician judgment. Curated by OPDSTAR (https://opdstar.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoICD-10-CM code, with or without dot. Examples: 'L20.9', 'L209', 'l20.9'. Auto-normalized (uppercased; tries dotted + undotted forms).
keywordNoFree-text search across English description, Chinese description, and code prefix. Examples: 'eczema', '皮膚炎', 'L20'.
langNoWhich description language(s) to include in the result. Default 'both'.both
limitNoMax results (1..50). Default 10.
Behavior4/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context that it is 'Reference only — clinical coding decisions require physician judgment' and mentions curation by OPDSTAR, which adds value beyond annotations. 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?

The description is well-structured and front-loaded: purpose first, then usage guidelines, then scope. Every sentence adds value without redundancy. It is appropriately sized for the tool's complexity.

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?

The description explains what the tool returns (descriptions, category, specialties) but does not detail the return format or pagination behavior. Given that there is no output schema and annotations are rich, the description is mostly complete for a lookup tool. Minor gap in not describing result structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters. The description provides example values for code and keyword (e.g., 'L20.9', 'eczema'), but does not add significant meaning beyond what is in the schema. Baseline score of 3 is appropriate.

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 it looks up ICD-10-CM diagnosis codes with descriptions, category, and OPDSTAR specialties. It differentiates from sibling tools by mentioning typical follow-ups like get_procedures_for_icd and check_icd_for_major_illness_eligibility, and includes a scope note about the Taiwan-specific subset.

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 when' scenarios (encountering ICD-10 code or free-text search) and provides typical follow-up chains. Also clarifies scope (Taiwan subset, not full CMS) and out-of-scope items (SNOMED, ICD-10-PCS), giving clear guidance on 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.

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/tatsuju/opdstar-nhi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server