Skip to main content
Glama

lookup_preventive_service

Read-onlyIdempotent

Retrieve eligibility and subsidy details for Taiwan NHI preventive services including adult health checks, cancer screenings, prenatal care, and child dental programs.

Instructions

Browse Taiwan NHI preventive-care and screening services — adult health checks, the major cancer screenings (breast, cervical, colorectal, oral, lung LDCT), prenatal care, child preventive health, and child dental fluoride / pit-and-fissure sealant programs. Returns each service's target population, age / sex eligibility, subsidy frequency, and screening tool. Use when an agent needs to know who is eligible for a preventive service and how often it is subsidised (e.g. 'who can get a mammogram and how often', 'child fluoride coverage'). Reference only — eligibility and subsidy follow the official 衛生福利部 announcements; the screening provider confirms eligibility at the point of service. Curated by OPDSTAR (https://opdstar.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoOptional service category: 'adult_health_check', 'cancer_screening', 'prenatal_care', 'child_preventive', 'dental_preventive', or 'integrated_screening'. If omitted, returns all services.
keywordNoOptional Chinese keyword (e.g. '乳房', '子宮頸', '塗氟', '產檢') to filter by service name, screening tool, or target population.
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that the data is curated by OPDSTAR and eligibility must be confirmed by the provider, providing useful context without contradicting 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 front-loaded with the main purpose and provides detailed examples and usage notes. While concise, it could be slightly shorter, but every sentence adds value.

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 what is returned (target population, eligibility, frequency, screening tool). It also notes the source and limitations. For a lookup tool with two optional parameters, this is complete and informative.

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% with descriptions for both parameters. The description adds Chinese keyword examples (e.g., '乳房', '塗氟') and clarifies the purpose of each parameter, providing marginal added value beyond the schema.

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 browses Taiwan NHI preventive-care and screening services, listing specific examples like adult health checks, cancer screenings, and child dental programs. This distinguishes it from sibling tools which focus on drugs, ICD codes, and audit guidelines.

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 explicit 'Use when' guidance for eligibility and subsidy lookups, and states 'Reference only' to indicate it's informational. However, it lacks explicit exclusions or alternatives, though siblings are distinctly different.

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