Skip to main content
Glama

SolvingHealth federal health data

search_drug_labels

Search FDA structured drug labeling (SPL) for indications and boxed warnings. Use to check what a drug is labeled for.

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
qNoBrand or generic name
brandNoBrand name
limitNoMax results, 1-50
genericNoGeneric name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 disclosure burden; it does useful work by naming the underlying dataset (SPL) and the fields searched (indications, boxed warnings). It says nothing about result ordering, default/maximum result counts, matching behavior, or whether a missing result means unlabeled versus unmatched.

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?

Two sentences, front-loaded with the dataset and searchable fields, then the use case. No filler or restated title.

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 simple read-only search with fully documented parameters and no output schema, the definition tells an agent enough to pick the tool and call it. The only real gap is how the overlapping name filters interact, which is an edge case rather than a blocker.

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 four parameters including the 1-50 limit are already documented. The description adds no meaning beyond the schema, such as how the free-text q relates to the brand and generic filters or whether they combine, so the baseline 3 applies.

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?

States a specific verb and resource (search FDA structured drug labeling / SPL) and narrows the target fields to indications and boxed warnings. It is clearly distinguishable from the sibling FDA search tools, though it does not name them 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?

"Use to check what a drug is labeled for" gives a concrete usage context that maps to a real agent task, which most sibling tools lack. It does not state when not to use it or point to an alternative tool for related questions.

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.