Skip to main content
Glama

get_drug_label_intelligence

Read-only

FDA drug label intelligence from OpenFDA DailyMed extracts. Returns brand and generic names, manufacturer, route, indications summary, and warnings summary. Use for formulary review, pharmacology research, and adverse event context. Source: FDA drug labels. $0.10 standard. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify.

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": {
      "drug_name": "<drug_name>"
    },
    "name": "get_drug_label_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
drug_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the upstream source (OpenFDA DailyMed), the per-call price ($0.10), and an attestation/verification path. It stops short of stating rate limits, matching behavior, or failure modes.

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 opening two sentences are well front-loaded and earn their place. The closing attestation/verification sentence ('post-quantum signed settlement receipt', verify URL) is marketing-style boilerplate that consumes roughly a quarter of the text without helping an agent decide or invoke.

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 single-parameter, no-output-schema tool, listing return fields and cost is close to sufficient. The missing piece is drug_name matching semantics, which is the one thing an agent can get wrong here, and no output schema exists to compensate.

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?

One required parameter with 0% schema description coverage, so the description carries the burden. It implies the tool knows about both brand and generic names but never says whether drug_name should be brand, generic, or either, nor whether matching is exact or partial — a real gap for a 2-200 char free-text key.

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 uses a specific verb-and-resource framing ('FDA drug label intelligence from OpenFDA DailyMed extracts') and enumerates exactly what comes back (brand/generic names, manufacturer, route, indications, warnings). It clearly separates itself from recall- or adverse-event-oriented siblings by the field list, though it never names an alternative explicitly.

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?

It offers usage contexts ('formulary review, pharmacology research, adverse event context') but these are topic labels rather than when-to-use rules. 'Adverse event context' overlaps directly with the get_drug_adverse_events sibling and no boundary is drawn, so the agent must infer which tool to pick.

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