Skip to main content
Glama

get_procedures_for_icd

Read-onlyIdempotent

Retrieve NHI procedure codes relevant to a Taiwan ICD-10 diagnosis and medical specialty. Returns curated candidates ordered by relevance for clinical decision support.

Instructions

Given a Taiwan ICD-10 code and a medical specialty, return the NHI procedure codes plausibly applicable to that diagnosis within that specialty. Each result includes the procedure code, Chinese name, English name, nhi_points (payment points), and audit_notes (specialty-specific review caveats and risk hints). Results are ordered by curated relevance (most commonly applied codes first), capped at limit (default 10, max 20). Returns an empty list (not an error) when no curated mapping exists for the given (icd10, specialty) pair — this is common because the mapping is intentionally conservative. Use when an agent is drafting SOAP and needs a starting set of procedure codes for the diagnosis within the clinician's specialty context — e.g. dermatologist with L30.9 (chronic eczema) needs candidate procedure codes. Typical follow-up: for each candidate code, call lookup_fee_code({q: <code>}) to confirm current points and effective dates, and lookup_audit_clauses_for_procedure({procedure_code}) to surface any audit-clause caveats. Don't use as a billing source of truth — the original NHI fee schedule has no ICD field, this is a curated, intentionally conservative mapping that prefers false negatives over false positives; for the canonical fee-schedule entry of a known code, call lookup_fee_code. Reference only — final code selection remains the clinician's responsibility. Curated by OPDSTAR (https://opdstar.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
icd10YesRequired. ICD-10-CM code in standard `LNN.N` format (letter + 2 digits + optional decimal + 1-4 sub-digits). Whitespace is trimmed; case is preserved (ICD-10 letters are uppercase by convention). Match is exact-prefix (passing 'L30' may match 'L30.0' / 'L30.9' depending on curation granularity). Examples: 'L30.9' (chronic eczema, dermatology) / 'J06.9' (acute URI, family / ent / pediatrics) / 'H66.9' (otitis media, ent / pediatrics) / 'M25.5' (joint pain, orthopedics / pmr).
specialtyYesRequired. The clinician's specialty (lowercase ID). Curated mappings differ by specialty because procedure relevance is specialty-specific (e.g. L30.9 in dermatology surfaces topical-treatment codes; in family medicine surfaces general-care codes). Pass the closest match — e.g. 'internal' for internal medicine, 'obstetrics_gynecology' for OB/GYN, 'tcm' for traditional Chinese medicine.
limitNoOptional. Maximum number of procedure-code candidates to return, ordered by curated relevance. Range 1-20. Default 10. Lower limits (3-5) work well when the agent only needs the top candidates; higher limits help when the diagnosis is broad and many codes may apply.
Behavior5/5

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

The description goes beyond annotations by explaining that the mapping is curated, intentionally conservative with preference for false negatives, and that results are ordered by relevance. It clarifies that an empty list is normal (not an error). No contradiction with annotations (readOnlyHint etc.).

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 structured with clear paragraphs: purpose, output, behavior, usage, follow-up, caveats, and source. Each sentence is informative and not redundant. It is appropriately sized for the tool's complexity without being overly verbose.

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 tool has 3 parameters, no output schema, and is used within a clinical workflow, the description thoroughly covers all aspects: input constraints, output format, empty list behavior, conservative mapping, and even references the source (OPDSTAR). It provides complete guidance for an agent to use correctly.

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

Parameters5/5

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

The input schema already provides full descriptions (100% coverage), but the description adds valuable context: for icd10 it explains exact-prefix matching and examples, for specialty it explains relevance per specialty, and for limit it states default and recommended lower/higher values. This adds clear meaning 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 states the tool's purpose: given a Taiwan ICD-10 code and medical specialty, return NHI procedure codes. It specifies the output fields (procedure code, Chinese name, English name, nhi_points, audit_notes) and ordering. It distinguishes from sibling tools like lookup_fee_code and lookup_audit_clauses_for_procedure.

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 says 'Use when an agent is drafting SOAP...' and provides typical follow-up actions. It also explicitly states 'Don't use as a billing source of truth' and explains why, plus references alternative tools. This covers both when to use and when not to.

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