Skip to main content
Glama

lookup_chronic_prescription_rule

Read-onlyIdempotent

Determine if an ICD-10 code or disease name is eligible for Taiwan NHI chronic-disease continuous-prescription and retrieve its dispensing limits (max days per dispense, total days, validity).

Instructions

Look up Taiwan NHI chronic-disease continuous-prescription (慢性病連續處方箋) rules. Given an ICD-10 code or a disease name, returns whether the condition falls within the official chronic-disease scope and its dispensing limits — maximum days per dispense, maximum total medication days, and prescription validity. Use when an agent needs to know if a diagnosis qualifies for a continuous prescription and the applicable day limits. Reference only — the issuing physician must confirm the patient's condition is stable and that the same long-term medication applies, per the official 全民健康保險醫療辦法 慢性病範圍. Curated by OPDSTAR (https://opdstar.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
icd_codeNoOptional ICD-10 code (e.g. 'I10', 'E11.9'). Prefix-matched against each chronic disease's ICD-10 range.
diseaseNoOptional Chinese disease name keyword (e.g. '高血壓', '糖尿病', '氣喘').
categoryNoOptional disease category (e.g. 'cardiovascular', 'endocrine_metabolic', 'respiratory', 'psychiatric').
Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context by emphasizing the tool is a 'Reference only' and mentions the need for physician confirmation, which goes beyond annotations. 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?

The description is moderately concise (about 100 words) and front-loads the main purpose. It uses formatting (bold) to highlight usage guidance. Every sentence adds value, though some details could be streamlined.

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?

Despite no output schema, the description fully explains what the tool returns: whether the condition qualifies and the specific dispensing limits. It also mentions the data source and official regulation, making it complete for a lookup tool with good annotations.

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%, so the baseline is 3. The description repeats some parameter information (e.g., 'Given an ICD-10 code or a disease name') but does not add significant value beyond what the schema already provides for each parameter.

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 looks up Taiwan NHI chronic-disease continuous-prescription rules, specifying inputs (ICD-10 code or disease name) and outputs (qualification and dispensing limits). It distinguishes this tool from sibling tools like lookup_major_illness by focusing on chronic prescription specifically.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes an explicit 'Use when' clause indicating the exact scenario for using this tool. It also provides a caution that it is for reference only and requires physician confirmation. However, it does not explicitly mention when not to use or suggest 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