Skip to main content
Glama

FDA drug label extract: renal, hepatic, boxed warning

rx_label_extract
Read-only

AI extraction from the FDA drug label (openFDA SPL) for an NDC, RxCUI or drug name: boxed warning, indications, dosage forms, renal and hepatic dose adjustment, contraindications, pregnancy and lactation, drug interactions, storage. Per section: short summary and points with verbatim label quotes checked in code, plus SPL set ID, version, effective date and DailyMed link. Generated by Anthropic Claude; summarizes FDA labeling, not medical advice. Price: $0.02 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged. AI-generated answer; a call with no arguments returns the stored example answer without a model call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rx_label_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
ndcNoNDC in any FDA layout: 10-digit dashed (4-4-2, 5-3-2, 5-4-1), 11-digit (5-4-2) or undashed. Give exactly one of ndc, rxcui or drug.
drugNoGeneric or brand drug name only, e.g. Eliquis, metformin, amoxicillin clavulanate. Inputs with patient details (age, weight, kidney values, my, patient) are rejected.
rxcuiNoRxNorm RxCUI. Product-level concepts (SCD, SBD, packs) match labels that list them; ingredient and brand concepts use the drug-name label selection.
sectionsNoComma-separated sections (default all): boxed_warning, indications, dosage_forms, renal_adjustment, hepatic_adjustment, contraindications, pregnancy_lactation, interactions_summary, storage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond readOnlyHint/openWorldHint: per-call pricing of $0.02 with USDC/x402 settlement, the rule that failed or non-matching calls are free, that answers are AI-generated summaries rather than medical advice, that quotes are verified in code, and that an argument-free call returns a cached example with no model call. These are exactly the cost, safety and edge-case facts an agent needs before invoking it.

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?

Front-loads purpose first, then output shape, then pricing and disclaimers; every sentence carries information. The single dense paragraph is long and could be split for scanability, but no sentence is filler.

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 exists, yet the description fully describes the return: per-section summary and points with verbatim label quotes checked in code, plus SPL set ID, version, effective date and DailyMed link. Combined with the input and pricing details, an agent has everything needed to call and interpret results.

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 description coverage is 100%, so each parameter is already documented in the input schema, and the description only echoes the three identifier types plus the section list. It adds no new syntax or format detail beyond what the schema already provides, 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 and resource ('AI extraction from the FDA drug label (openFDA SPL)') and enumerates exactly which label sections are returned, so an agent can tell it apart from a general drug or NDC lookup sibling without opening the schema.

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?

Gives clear context: supply one of NDC, RxCUI or drug name, and use `sections` to scope down to specific sections. It also flags the unusual no-argument path that returns a stored example instead of doing work. It stops short of naming when to prefer a sibling label or drug tool instead.

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