Skip to main content
Glama

search_nhi_interpretations

Read-onlyIdempotent

Find official NHI administrative interpretations (函釋) that clarify how payment rules, drug coverage, and review policies apply. Use when you need an official ruling rather than a code definition.

Instructions

Search Taiwan's official NHI administrative interpretations (健保署行政函釋 / 函令) — the binding 公告 and 解釋函 issued by the National Health Insurance Administration that clarify how payment rules, drug-formulary provisions, special-material coverage, and review policy apply in practice. Each result returns the official document number (字號), issue date, 主旨 (subject), a content excerpt, and the source URL on the government law portal. Returns up to 10 ranked excerpts (most relevant first); returns an empty list (not an error) when nothing matches. Use when a question turns on an official ruling rather than a code definition — e.g. '函釋怎麼說人工水晶體的給付規定' / 'is there an interpretation on continuous-prescription day limits' — or when the user cites a 函釋 文號 directly (e.g. 健保審字第 1090017813 號). Don't use when you already have a specific rejection code, fee code, or drug name — those have dedicated lookup tools (lookup_rejection_code, lookup_fee_code, lookup_drug). Reference only — the official 健保署 / 衛福部 publication is authoritative; an excerpt may lag the latest revision and is not the full document, so open the source URL for the binding text. Curated by OPDSTAR (https://opdstar.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesRequired. Natural-language query in Traditional Chinese or English, OR a 函釋 document number. Multi-word phrases work best (concept + qualifier). Examples: "人工水晶體 給付規定" / "continuous prescription day limit interpretation" / "健保審字第1090017813號". Single characters or 1-letter strings are unlikely to return useful matches.
limitNoOptional. Maximum number of ranked excerpts to return. Range 1-10. Default 5. Increase to 10 when surveying a topic; keep at 5 for a targeted look-up to save context.
Behavior5/5

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

Annotations already mark readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds that it is a reference only, the official publication is authoritative, excerpts may lag, and to open the source URL for binding text. No contradiction.

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 with purpose first, then output details, usage guidance, and caveats. Every sentence adds value but could be slightly more concise (e.g., 'excerpt may lag the latest revision and is not the full document' could be shortened).

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?

For a search tool, description covers ranking (top 10), error behavior (empty list not error), return format, and important caveats (reference only, authoritative source, open URL for binding text). No output schema needed.

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% with descriptions for both parameters. Description adds practical guidance: query can be natural language or document number, multi-word phrases best, single characters unlikely to work; limit usage advice (increase for survey, keep low for targeted lookup).

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 searches Taiwan's NHI administrative interpretations, specifies the returned fields (document number, issue date, subject, excerpt, URL), and distinguishes from sibling tools by listing when not to use it (rejection code, fee code, drug name).

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' and 'Don't use' with concrete examples (e.g., '函釋怎麼說人工水晶體的給付規定', '健保審字第1090017813號'), and names alternative sibling tools like lookup_rejection_code.

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