Skip to main content
Glama

search_drug_labels

Search FDA drug product labeling by brand name, generic name, manufacturer, active ingredient, indication, or route. Retrieve up to 100 results with pagination support.

Instructions

Search FDA drug product labeling information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brand_nameNoBrand/trade name of the drug
generic_nameNoGeneric name of the drug
manufacturerNoManufacturer name
active_ingredientNoActive ingredient name
indicationNoMedical indication or condition
routeNoRoute of administration (e.g., ORAL, TOPICAL)
product_typeNoProduct type (e.g., HUMAN PRESCRIPTION DRUG)
countNoField to group results by for counting
limitNoMaximum number of results to return (1-100)
skipNoNumber of results to skip for pagination
Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits (e.g., read-only vs. mutating, authentication, rate limits, response format). The agent has no insight into tool effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but lacks necessary detail for an agent to use effectively. It is not structured to highlight key aspects.

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

Completeness1/5

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

With 10 parameters and no output schema or annotations, the description is extremely sparse. It does not explain what 'labeling information' includes, how search results are returned, or any pagination behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While schema description coverage is 100%, the description adds no additional meaning beyond parameter names and types. Baseline 3 is lowered because the description does not enhance understanding of how parameters interact or are used in search.

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 clearly states the tool searches FDA drug product labeling information. However, it does not differentiate from sibling tools like search_drugs_fda, which may also return labeling-related data.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as search_drug_adverse_events or search_drug_recalls. The agent receives no context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Augmented-Nature/OpenFDA-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server