Skip to main content
Glama

search_drug_labels

Search FDA drug labeling for prescribing information, indications, warnings, dosage, and active ingredients; filter by boxed warnings or retrieve specific label sections by set ID.

Instructions

Search FDA drug labeling (SPL) information including prescribing information, indications, warnings, boxed warnings, dosage, and active ingredients. Retrieve a specific label by setId. Filter for drugs with boxed warnings using hasBoxedWarning. Request specific sections (e.g., indications_and_usage, adverse_reactions, boxed_warning) to limit response.

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": "search_drug_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of results to skip for pagination
limitNoMaximum results to return (1-100, default 10)
routeNoRoute of administration (e.g., 'oral', 'intravenous')
setIdNoUnique label identifier (set_id) for retrieving a specific drug label
drugNameNoDrug brand or generic name
sectionsNoSpecific label sections to return (e.g., ['indications_and_usage', 'warnings', 'adverse_reactions'])
indicationNoMedical indication or use case
hasBoxedWarningNoFilter for drugs with boxed warnings (most serious safety warnings)
activeIngredientNoActive ingredient/substance name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully signals that requesting sections limits the response payload, which is a real behavioral trait, but it never states what happens when sections is omitted (full label?), how multiple filters combine, or what an invalid setId returns. Auth, rate-limit, and output-shape behavior are all undisclosed.

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?

Three sentences, each front-loaded with a distinct capability, and the core search purpose comes first. The opening sentence is a fairly dense feature list, but every clause maps to actual queryable content and nothing is redundant filler.

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

Completeness3/5

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

For a nine-parameter tool with no annotations and no output schema, the description covers the main query modes but omits default behavior (no filters at all returns what?), filter-combination semantics, and response shape. It also leaves pagination entirely to the schema's limit/skip defaults.

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 all nine parameters are already documented, establishing a baseline of 3. The description reinforces the intent of setId, hasBoxedWarning, and sections with examples, but adds little syntax or meaning the schema does not already supply.

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 pairs a specific verb ("Search") with a precise resource ("FDA drug labeling (SPL) information") and enumerates the content types covered: prescribing information, indications, warnings, dosage, active ingredients. That is enough to distinguish it in practice from siblings such as search_drug_adverse_events or search_drug_ndc, though no sibling is named explicitly.

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?

It describes three distinct usage modes with the parameter that selects each: single-label retrieval via setId, boxed-warning filtering via hasBoxedWarning, and section-limited responses via sections. There is no explicit when-not-to-use guidance or routing to the adverse-events/NDC/recalls siblings, so it stops short of a 5.

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