Skip to main content
Glama

search_audit_guidelines

Read-onlyIdempotent

Search Taiwan NHI audit guidelines by keyword to get summaries of relevant rules and suggestions. Use to explore coverage of topics like antibiotics or test frequencies.

Instructions

Free-text search over Taiwan NHI 審查注意事項 rules — returns reason + suggestion summaries (first sentence only) for up to 10 rules matching a keyword (Traditional Chinese or English). Use when an agent is exploring whether any audit rule covers a topic (e.g. '抗生素', '檢查頻率', '慢性病處方') without knowing a specific code. Don't use for clauses tied to a known procedure code — call lookup_audit_clauses_for_procedure instead. Full SOAP example templates and detailed reasoning are part of the paid OPDSTAR product. Reference only — official 健保署 審查注意事項 is authoritative; results are previews. Curated by OPDSTAR (https://opdstar.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesFree-text query (2+ chars), Traditional Chinese or English. Examples: '抗生素', '檢查頻率', '慢性病處方'.
specialtyNoOptional specialty filter (e.g. 'tcm', 'dermatology'). Omit to search all specialties.
Behavior5/5

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

Beyond annotations, description discloses result limitations (first sentence only, up to 10 results), preview nature, and authoritative source, adding significant context.

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?

Description is concise with front-loaded main action, followed by usage and disclaimers, no unnecessary text.

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 no output schema, description effectively explains return value structure (reason+suggestion, first sentence, max 10) and provides context about tool purpose and limitations.

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?

Schema coverage is 100%, so baseline is 3. Description provides examples matching schema but does not add new semantic details about parameters.

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 performs free-text search over Taiwan NHI audit rules and returns summaries, differentiating from siblings like 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 provides 'Use when' and 'Don't use' guidance with examples, and names the alternative tool for specific procedure codes.

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