Skip to main content
Glama

lookup_fee_code

Read-onlyIdempotent

Search the Taiwan NHI fee schedule by code or name to retrieve points, effective dates, and audit notes.

Instructions

Look up the Taiwan NHI fee schedule (全民健康保險醫療服務給付項目及支付標準, current effective edition). Search by exact code (e.g. '00101B', 'P15001') or by Chinese / English name (e.g. '門診診察', 'ICU') — returns code, points, effective dates, and audit notes (truncated to 600 chars). Use category prefix to scope ('00' 基本診療, '06' 手術, 'P1' 病例計酬, 'N2' 護理). Use when an agent needs the canonical fee entry for a known procedure code, or wants to discover codes by name. Don't use for drugs (call lookup_drug) or for ICD-10 → procedure suggestions (call get_procedures_for_icd). The optional icd filter applies an OPDSTAR-curated mapping that is intentionally sparse (the original NHI data has no ICD field) — most codes will return no result with icd active. Reference only — official 健保署 支付標準 is authoritative. Curated by OPDSTAR (https://opdstar.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesRequired ≥2 chars. Exact code match for 2-8 char alphanumerics (e.g. '00101B', 'OT1', 'P15001'); otherwise ILIKE search across name_zh + name_en. Examples: '00101B', '門診診察費', 'ICU', '麻醉', 'physical therapy'.
categoryNoOptional 1-2 char category prefix filter. Examples: '00' 基本診療, '01' 麻醉, '06' 手術, '08' 檢驗, 'P1'/'P4' 病例計酬, 'N2' 護理, 'A0'-'D9' 牙醫.
icdNoOptional ICD-10 code to filter by OPDSTAR-curated applicable_icd_pattern. NOTE: this mapping is sparse — original NHI data has no ICD field; OPDSTAR enriches incrementally. Most codes will return no result with icd filter active.
Behavior5/5

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

Annotations already declare readOnly, non-destructive, idempotent. Description adds that audit notes are truncated to 600 chars, icd filter is sparse, and tool is reference only. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single paragraph but well-organized, each sentence adds value. Could be slightly more structured but remains clear and efficient.

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?

Covers purpose, parameters, return fields (code, points, dates, audit notes truncated), caveats (sparse icd, reference only), and examples. Adequate given 3 params and no output schema.

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?

Schema coverage is 100%. Description adds context: how q matches (exact vs ILIKE), examples, category prefix meanings, and icd sparsity. This meaningfully extends 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?

Description specifies verb 'Look up' and resource 'Taiwan NHI fee schedule', details search by code or name, and explicitly distinguishes from siblings by stating not to use for drugs or ICD-10 procedure suggestions.

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?

Provides clear 'Use when' and 'Don't use' guidance, explains category prefix usage, mentions sparse icd filter, and references alternative tools (lookup_drug, get_procedures_for_icd).

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