Skip to main content
Glama

recent_nhi_amendments

Read-onlyIdempotent

List recent amendments to Taiwan NHI rules and audit guidelines. Get effective dates, amendment titles, and official announcement links to track upcoming changes.

Instructions

List recent amendments to Taiwan NHI rules and audit guidelines (健保署「醫療費用審查注意事項」近一年修正公告). Returns the publication / effective dates, the amendment title and type ('primary' = main regulation update, 'comparison' = side-by-side diff document), and direct links to the official DOCX / ODT / PDF announcement files plus the 健保署 listing page. Use when an agent needs to answer 'what NHI rule changes are coming?', 'when does the new 審查注意事項 take effect?', or wants to check whether a specific rule has been recently amended before quoting it. Typical follow-up: call search_audit_guidelines({query}) to pull the post-amendment clause text, or lookup_rejection_code({code}) to see how it ties into existing rejection codes. Reference only — official 健保署 announcements are authoritative. Curated by OPDSTAR (https://opdstar.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
since_daysNoLimit to amendments effective within N days from today (1..3650). Default 365 (近一年).
typeNo'primary' = main regulation update (affects nhi_audit_clauses content); 'comparison' = side-by-side diff document. 'all' returns both. Default 'all'.all
limitNoMax results (1..50). Default 20.
Behavior4/5

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

Annotations already provide readOnlyHint=true and idempotentHint=true, so the description's main contribution is detailing the output structure (dates, title, type, links) and stating that it is curated by OPDSTAR and not authoritative. This adds valuable context beyond 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?

The description is well-structured with purpose stated first, followed by use cases and follow-ups. It is informative but slightly verbose; however, it earns its content without being overly long.

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, the description explains output fields (dates, title, type, links) and includes links to official files. Annotations are complete, and sibling tools are mentioned in context. The description is fully adequate for the tool's complexity.

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 description coverage is 100% with full descriptions for all three parameters. The description does not add new information about input parameters beyond what is already in the schema, so the baseline of 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?

The description clearly states the tool lists recent amendments to Taiwan NHI rules and audit guidelines, with specific use cases like 'what NHI rule changes are coming?'. It distinguishes itself from siblings by mentioning typical follow-ups to other tools like search_audit_guidelines and lookup_rejection_code.

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?

The description explicitly provides when to use the tool ('Use when an agent needs to answer...'), typical follow-up actions, and a note that it's for reference only with official announcements being authoritative. This gives clear guidance on context and alternatives.

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