MCP server for drug disambiguation against RxNorm Current Prescribable Content
Server has 7 tools with complete input schemas and descriptions. Naming follows verb_noun convention (search_drugs, start_drug_disambiguation, etc.). Descriptions are present and contextual (50-150 chars), explaining WHAT and WHEN. However, parameter descriptions lack detail on constraints, formats, and valid ranges. The 'state' parameter (used in 3 tools) is documented as 'Current disambiguation state' but lacks schema detail on its structure. Output schemas are not documented in the tool definitions. Error handling guidance is minimal, no recovery hints or actionable error messages visible in the code sample.
Apply the user's answer to a returned question and produce new state.
Inspect one RxNorm concept and its surrounding ambiguity context.
Reverse-lookup a raw or normalized NDC against RxNorm SCD/SBD products.
Return the next required drug-scope question, or null if resolved. If a question is returned, present its prompt and options to the user. Do not invent options outside the returned list.
Resolve a fully answered drug-disambiguation state to NDCs and summary.
Search RxNorm drug concepts by name and return candidate concepts. Pick a candidate RXCUI only when the user's intended drug is clear. If multiple candidates plausibly refer to different ingredients or product families, ask the user which candidate they mean before starting.
State parameter lacks schema documentation. Tools 'next_drug_question', 'answer_drug_question', and 'resolve_drug_scope' accept a 'state' object but provide no schema, field names, or structure guidance. LLMs cannot construct or validate state objects without this.
Output schemas not documented. No tool definition includes a documented return type or response structure. LLMs cannot plan downstream calls or extract required fields (e.g., what does resolve_drug_scope return? NDC list? Summary object?).
Parameter constraints missing. 'limit' in search_drugs has a default (10) but no min/max bounds. 'rxcui' is typed as integer but no range or validation guidance. 'values' in answer_drug_question is an array but no element type or length constraints.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
Start a disambiguation session for a selected RxNorm concept.
No error recovery guidance. Tool descriptions do not explain what to do if a drug is not found, if disambiguation fails, or if an NDC is invalid. Agents have no fallback strategy.
Composition risk: 'answer_drug_question' requires both 'state' and 'key' parameters, but no guidance on how to obtain 'key' from the prior 'next_drug_question' response. Chaining is implicit, not documented.