Skip to main content
Glama

get_indicator

Read-onlyIdempotent

Retrieve the human-readable explanation for a Taiwan NHI prescribing-pattern indicator code. Get the indicator name, threshold, applicable drugs/diagnoses, and compliance meaning for codes like '008' or 'P043'.

Instructions

Look up a single Taiwan NHI prescribing-pattern indicator. These are 1-4 character codes that encode common over-prescribing patterns: 3-digit numeric codes (e.g. '008' antibiotic-on-URI, '014' multi-PPI co-prescribing, '027' duration limit) or 'P'-prefixed codes (e.g. 'P043' chronic-prescription duration cap). Returns the indicator name, the threshold (e.g. '7-day URI episode'), applicable drugs / diagnoses, and the compliance meaning. Returns a not-found message (not an error) if the code does not exist. Use when an agent needs the human-readable explanation for a specific indicator code referenced during a SOAP review or audit response — e.g. an audit notice cites indicator 008 and the agent needs to surface what 008 monitors and why a prescription tripped it. Typical follow-up: call get_drug_rules({rejection_code}) with the indicator's downstream rejection code to read the formal payment rule, or search_audit_guidelines({query}) to read related audit-clause text. Don't use for the official 分析審查不予支付指標 (percentage-cap audit) list — that's a different system — call lookup_audit_indicator instead. Reference only — thresholds and applicable lists reflect published guidance and may change with each NHI release; agents should re-read the indicator each session rather than caching values across sessions. Curated by OPDSTAR (https://opdstar.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesRequired. The exact prescribing-pattern indicator code. Format: 1-3 digits (e.g. '008', '014', '027') OR 'P' + 1-3 digits (e.g. 'P043', 'P018'). Whitespace is trimmed. Numeric codes are NOT zero-padded automatically — pass '008' not '8'. Lowercase 'p' is accepted but normalized to uppercase. Examples: '008' (抗生素開立於 URI), '014' (multi-PPI co-prescribing), '027' (用藥日數上限), 'P043' (慢性處方箋日數上限).
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint false, idempotentHint true. The description goes beyond by disclosing: returns a 'not-found message (not an error)' for invalid codes, is reference-only with volatile thresholds (should re-read each session), and states curation source. No contradictions with 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 comprehensive but slightly verbose. However, it is well-structured with bolded instructions, clear sections, and front-loaded purpose. Each sentence serves a purpose, though some redundancy exists (e.g., repeating code formats). Still, it efficiently conveys necessary information.

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 the lack of output schema, the description fully explains what is returned: indicator name, threshold, applicable drugs/diagnoses, compliance meaning, and not-found behavior. It also provides examples and typical follow-ups, ensuring an agent can use the tool without ambiguity.

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

Parameters5/5

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

Schema description coverage is 100% for the single `code` parameter, with format rules and examples. The description adds context beyond schema: explains zero-padding requirement, case normalization, and typical examples like '008' or 'P043'. This extra detail aids correct usage.

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's purpose: 'Look up a single Taiwan NHI prescribing-pattern indicator.' It specifies the exact codes (1-4 character codes, numeric or P-prefixed) and distinguishes from a sibling tool (`lookup_audit_indicator`) by explicitly saying when not to use it.

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 explicit usage context: 'Use when an agent needs the human-readable explanation for a specific indicator code referenced during a SOAP review or audit response.' Includes typical follow-up calls and an explicit exclusion: 'Don't use for the official 分析審查不予支付指標 (percentage-cap audit) list.' This clearly guides the agent on when to invoke this tool versus 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