Skip to main content
Glama

lookup_rejection_code

Read-onlyIdempotent

Look up a Taiwan NHI rejection code by its 5-character code (e.g., 0317A) to get severity, category, and the official Chinese description from 健保署. Useful for understanding claim rejection reasons.

Instructions

Look up a single Taiwan NHI rejection code (5-character format NNNNL — 4 digits + 1 uppercase letter A/B/C/..., e.g. '0317A', '0338A', '0114A'). Returns severity (low / medium / high), category (00 診療品質 · 01 病歷紀錄 · 02 基本診療 · 03 藥品特材 · 04 手術處置 · 05 檢查檢驗 · 06 論病例計酬 · 07 復健精神 · 08 其他 · 09 法令 — first two digits encode the category), and the official Chinese description from 健保署 專業審查不予支付理由代碼. Returns a not-found message (not an error) if the code does not exist. Use when an agent encounters a known rejection code in a notice or claim response and needs the human-readable explanation, or when triaging which category a code belongs to. Typical follow-up: call get_drug_rules({rejection_code}) if the code is in category 03 (藥品特材) to surface the drug rule behind the rejection; call search_audit_guidelines({query: <code>}) for codes in 04 / 05 to read the underlying audit-clause text; call count_appeal_precedents_for_rejection_code({rejection_code}) to gauge whether disputes for this code are commonly successful. Don't use to enumerate codes by category — call get_rejection_code_category({category}) instead. Reference only — the official 健保署 code list is authoritative. Curated by OPDSTAR (https://opdstar.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesRequired. The exact 5-character NHI rejection code in `NNNNL` format (4 digits followed by 1 uppercase letter). Lowercase letters are auto-uppercased; whitespace is trimmed. Examples: '0317A' (病歷紀錄不全) / '0338A' (藥品特材) / '0114A' (病歷紀錄). The first two digits identify the category (00-09).
Behavior5/5

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

Annotations indicate read-only, non-destructive, idempotent. Description adds that a not-found message (not an error) is returned for non-existent codes, and that input is auto-uppercased and whitespace-trimmed. No contradiction with annotations.

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?

Well-structured and front-loaded with purpose, then usage. Slightly verbose but every sentence adds value. Could be slightly more concise, but still highly effective.

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?

Completely covers what the tool does, its return behavior, usage context, and limitations. No output schema but description adequately explains return values.

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?

Input schema has one param with 100% coverage. Description adds examples, format explanation, and auto-uppercase behavior, adding value 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 looks up a single Taiwan NHI rejection code, specifying the exact format and what it returns (severity, category, Chinese description). It distinguishes itself from siblings like get_rejection_code_category which enumerates codes by category.

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 when to use (encounter a known rejection code, triaging category) and when not to use (enumerating codes), and provides typical follow-up actions. Also mentions reference only and authoritative source.

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