Skip to main content
Glama

Drug card: RxNorm, FDA label, DEA schedule, shortages

rx_drug
Read-only

Drug card for a generic or brand name: RxNorm concept (RxCUI, ingredients, brands); one openFDA label (brand checked against RxNorm ingredients, else single-ingredient full prescribing info, most common route, earliest NDA/BLA) with clipped boxed warning, indications, dosing, contraindications, warnings, interactions, pregnancy, lactation, special-formulation flag, other routes, DailyMed link; DEA schedule and status (NDC data); FDA shortage and 2-year recall summaries. Price: $0.02 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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": {
      "name": "<name>"
    },
    "name": "rx_drug"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesGeneric or brand drug name, e.g. lipitor, metformin, Eliquis, amoxicillin clavulanate, Tylenol #3. A route or formulation word (oral, iv, liposomal) narrows the label choice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the description only needs to add context. It does that well: label-selection heuristics (brand matched against RxNorm ingredients, else single-ingredient full prescribing info, most common route, earliest NDA/BLA), clipped sections, a $0.02 per-successful-call x402/USDC charge, and no charge on failure or no-match. However, selection heuristics and cost details do not describe the result's structure or how ambiguity is resolved.

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?

Dense but front-loaded: purpose first, then contents, then pricing. The semicolon-separated inventory is efficient, though the clipped-section list is long enough to slow scanning slightly.

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?

No output schema exists, so the description must explain return content and does so thoroughly, plus selection logic and cost. It leaves out minor items such as error/no-match response shape and how conflicting names are handled, which keeps it below top marks.

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?

One parameter with 100% schema coverage sets the baseline at 3. The schema already explains the generic/brand name and that route/formulation words narrow label choice; the description only echoes 'most common route' and 'other routes' without adding input syntax or ambiguity behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely ('Drug card for a generic or brand name') and enumerates its components: RxNorm concept, one openFDA label, DEA schedule/status, shortage and recall summaries. It's a clear composite-tool statement. It stops short of naming a sibling like rx_label_extract or rx_shortages, so an agent must infer the subset relationships itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: pass a drug name, receive a consolidated card, and unmatched calls cost nothing, which encourages trying. There is no explicit guidance about when to choose this over the narrower siblings (rx_label_extract, rx_shortages, rx_ndc, rx_price) when the agent needs only one component.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources