Skip to main content
Glama

lookup_drug

Read-onlyIdempotent

Search the Taiwan NHI drug catalog by generic name, brand name, or drug code to retrieve up to 10 matching drugs with strength, dosage form, route, ATC code, and therapeutic class.

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 context: 'Reference only — official... is authoritative; catalog is a working snapshot', and mentions result limit of 10. 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?

Concise, front-loaded purpose, usage guidance, alternatives, and disclaimers. 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?

No output schema, but description specifies return fields (strength, dosage form, route, ATC code, therapeutic class, brand list) and limit of 10 matches. Input parameters fully documented in schema. Complete for a lookup 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 parameter descriptions. The description does not add new parameter semantics but summarizes search fields. Baseline 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 verb 'look up', the resource 'active Taiwan NHI drug catalog', and lists return fields (strength, dosage form, etc.). It distinguishes from sibling tools by specifying search terms (generic name, brand name, code, alias).

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 states when to use (identify/disambiguate drug before dosage/formulation) and when not to use (payment rules, audit clauses), with alternative tool names get_drug_rules and 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