Skip to main content
Glama
mymedi-ai-mcp-server

mymedi-ai-mcp-server

by MyMedi-AI

RxNorm drug normalization (NIH)

drug_rxnorm
Read-only

Normalize a drug name with NIH RxNorm to retrieve matching concepts, RxCUI, synonyms, term types, and primary RxCUI; it does not check interactions.

Instructions

Normalize a drug name with NIH RxNorm: returns the matching RxNorm concepts (RxCUI, name, synonym, term type) and the primary RxCUI. It does not check interactions. Source: RxNorm, from the U.S. National Library of Medicine (RxNav API).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "drugName": "<drugName>"
    },
    "name": "drug_rxnorm"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugNameYesDrug name to look up (min 2 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.9
    • removedInput schema / properties / checkInteractions
      Removed value: -{
      -  "description": "Other drug names to check for clinical interactions against the primary drug",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • addedInput schema / properties / drugName / maxLength
      Added value: +500
  2. Addedv1.2.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety and external-dependency profile is covered; the description adds value by naming the underlying service (RxNav API, NLM) and by enumerating the returned concept fields since there is no output schema. It omits practical traits such as how multiple candidates are ranked, whether the primary RxCUI is deterministic, and any latency/rate-limit behavior.

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?

Three short sentences, front-loaded with the verb and resource, then return shape, then the negative scope and source. No filler and no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, no-output-schema lookup tool this covers what the agent needs: what comes back, what it does not do, and where the data originates. The remaining gap is how ambiguous or multi-match names are handled and whether the 'primary RxCUI' is a best-match or a fixed selection.

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?

There is a single parameter with 100% schema description coverage ('Drug name to look up (min 2 chars)'), so the schema already carries the semantics. The description only echoes 'a drug name' without adding guidance on what forms are accepted (brand vs generic, combination products, dosage forms), so the 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?

States a specific verb+resource ('Normalize a drug name with NIH RxNorm') and enumerates the return fields (RxCUI, name, synonym, term type, primary RxCUI). The explicit exclusion ('does not check interactions') cleanly separates it from the drug_interactions sibling, and the source attribution removes any ambiguity about which normalization system is used.

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 'does not check interactions' caveat gives the agent an explicit routing signal toward drug_interactions, which is real usage guidance. It stops short of distinguishing this from ambiguous siblings like drug_lookup and drug_enrich, leaving the agent to infer which one is the right normalization path.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.