Skip to main content
Glama

lookup_icd10_cm

Read-onlyIdempotent

Look up ICD-10-CM diagnosis codes by code or keyword to find English and Traditional Chinese descriptions, category, and related OPDSTAR specialties.

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.
Behavior5/5

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

Annotations already declare the tool as readOnly, non-destructive, and idempotent. The description adds key behavioral context: it is 'Reference only', requires physician judgment for clinical coding, and discloses data limitations (currently a ~3,000 code subset from OPDSTAR, with full set planned). This fully informs the agent of constraints and reliability.

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 moderately long but well-structured with bold headers, bullet points, and clear sections. Every sentence adds value, covering purpose, usage, scope, limitations, and follow-ups. Minor redundancy could be trimmed, but overall efficient for the information conveyed.

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?

Given the tool's simplicity and rich annotations/schema, the description is complete: it covers purpose, usage, behavioral constraints, parameter behavior, and scope. No output schema exists, but the description implies return of code, descriptions, category, and specialties. A brief note on result format would improve completeness slightly.

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 baseline is 3. The description adds value by explaining auto-normalization for the code parameter (uppercased, dotted/undotted forms), and clarifies that keyword searches across English, Chinese, and code prefix. This enhances understanding beyond the schema.

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 identifies the tool as a lookup for ICD-10-CM diagnosis codes with English/Chinese descriptions, category, and OPDSTAR specialties. It distinguishes itself from sibling tools by explicitly stating typical follow-up chains (get_procedures_for_icd, check_icd_for_major_illness_eligibility) and scope limitations (subset vs full set).

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?

The description explicitly states when to use ('when the agent encounters an ICD-10 code...needs canonical name, or wants to free-text search') and provides specific scenarios (note, claim, rejection notice). It also lists out-of-scope items (SNOMED CT, ICD-10-PCS) and directs to alternative tools for follow-ups.

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