Skip to main content
Glama

openfda_drug_search

Read-onlyIdempotent

Search FDA drug labels by brand name or ingredient to find drug information, with an optional result limit.

Instructions

Search FDA drug labels by brand name or ingredient.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results (default 5)
queryYesDrug name or ingredient to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds matching scope but does not expand on rate limits, authentication, result shape, or other behavioral context beyond what annotations and schema provide.

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?

The description is a single front-loaded sentence with no filler. It is appropriately sized for a simple two-parameter search tool.

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 read-only search tool with fully covered schema parameters and rich annotations, the description supplies the essential purpose and search scope. It does not describe returned label fields or search matching behavior, but no output schema exists and those details are secondary here.

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 the 'query' and 'limit' parameters are already documented in the schema. The description reinforces that 'query' matches brand name or ingredient, but adds no syntax or formatting details beyond the schema.

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?

The description names a specific verb ('Search'), resource ('FDA drug labels'), and matching fields ('brand name or ingredient'). It also implicitly distinguishes this from sibling OpenFDA endpoints such as openfda_recall_search and openfda_adverse_events by scoping the search to drug labels.

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 by the stated resource and matching fields: an agent can infer this is for drug label lookups by brand or ingredient. However, there is no explicit when/when-not guidance or routing to sibling tools like recall or adverse-event searches.

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

Deploy Server

Other Tools