Skip to main content
Glama

lookup_audit_clauses_for_procedure

Read-onlyIdempotent

Retrieve Taiwan NHI 審查注意事項 clauses referencing a procedure code, with risk flags for amount limits, frequency rules, or indication restrictions.

Instructions

Find Taiwan NHI 審查注意事項 clauses that reference a specific procedure code (e.g. '00101B', '51017C') — each result indicates whether the clause carries an amount limit, frequency rule, or indication restriction (critical signals for rejection-risk assessment). Returns clause summary, specialty, and risk flags. Use when an agent has a candidate procedure code and needs to surface the audit context attached to it. Don't use for the procedure's fee-schedule entry (points / effective dates) — call lookup_fee_code; for browsing all clauses within a specialty, call lookup_audit_clauses_for_specialty. Reference only — clause summaries are first-sentence previews; official 健保署 審查注意事項 is the source of truth. Curated by OPDSTAR (https://opdstar.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
procedure_codeYesRequired NHI procedure code (5-8 alphanumeric chars). Examples: '00101B', '51017C', 'P15001'. Case-insensitive.
specialtyNoOptional specialty filter (e.g. 'dermatology', 'internal_medicine', 'tcm'). Narrows the result to one specialty section.
Behavior5/5

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

Annotations already declare read-only, non-destructive, idempotent. Description adds critical behavioral details: returns risk flags, is a reference with warnings about authority, and specifies output includes clause summary and specialty.

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?

Concise yet comprehensive: front-loaded with purpose, then usage guidelines, then caveats. Every sentence adds value with no redundancy.

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 complexity (lookup with optional filter), annotations cover safety, and description fully explains return values (clause summary, specialty, risk flags) and limitations. No output schema needed.

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

Parameters3/5

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

Input schema covers both parameters with descriptions (100% coverage). Description does not add new parameter semantics beyond what schema already provides; baseline 3 is appropriate.

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 clearly states the tool finds audit clauses for a specific procedure code, with examples. It distinguishes from sibling tools like lookup_fee_code and lookup_audit_clauses_for_specialty.

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 when-to-use, when-not-to-use, and direct alternatives: 'Use when...' for audit context, 'Don't use for fee-schedule entry... call lookup_fee_code; for browsing all clauses within a specialty, call lookup_audit_clauses_for_specialty.'

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