Skip to main content
Glama

lookup_drug

Read-onlyIdempotent

Look up Taiwan NHI drug catalog by generic name, brand name, drug code, or alias to identify and disambiguate a drug before recommending dosage or formulation in a SOAP draft.

Instructions

Look up the active Taiwan NHI drug catalog by generic name, brand name, NHI drug code, or alias — returns up to 10 matches with strength, dosage form, route, ATC code, therapeutic class, and brand list. Use when an agent needs to identify or disambiguate a drug before recommending dosage / formulation in a SOAP draft. Don't use to look up payment / reimbursement rules for the drug — call get_drug_rules instead; for an audit clause referencing the drug, call search_audit_guidelines. Reference only — official 健保署 藥品給付項目及支付標準 is authoritative; the catalog is a working snapshot. Curated by OPDSTAR (https://opdstar.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesRequired ≥2 chars. Search across generic_name, brand_names, aliases, normalized_key. Also accepts NHI 9-10 char drug code (e.g. 'A02229715'). Examples: 'augmentin', 'amoxicillin', 'A02229715', '阿司匹林', 'lamisil'.
specialtyNoOptional specialty filter (e.g. 'dermatology', 'internal', 'pediatrics'). Only returns drugs tagged with this specialty.
dosage_formNoOptional dosage form filter: 'tablet', 'capsule', 'cream', 'ointment', 'syrup', 'solution', 'suspension', 'inj', 'supp', 'eye drops', 'ear drops', 'nasal spray', 'inhalation', 'patch', 'powder', 'gel', 'lotion', 'vaginal tablet'.
routeNoOptional route filter: 'oral', 'topical', 'injection', 'ophthalmic', 'otic', 'nasal', 'inhalation', 'rectal'.
Behavior4/5

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

Annotations already declare readOnlyHint true and idempotentHint true. Description adds that results are limited to 10 matches and that the catalog is a working snapshot, noting the official source is authoritative. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise, front-loaded with purpose, uses bold markers for use/don't use. 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?

Despite no output schema, the description enumerates return fields and states limitations (10 matches, working snapshot, authoritative source). Comprehensive for a search tool.

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 detailed descriptions including examples and constraints. Tool description does not add meaningfully beyond the schema, so baseline 3 applies.

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 looks up the Taiwan NHI drug catalog by multiple identifiers, returns up to 10 matches with specific fields. It distinguishes itself from siblings like search_taiwan_drug and get_drug_rules.

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 tells when to use (identify/disambiguate drug for SOAP draft) and when not to use (payment rules, audit clauses), with direct sibling tool names (get_drug_rules, search_audit_guidelines).

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