Crypto, web, finance and app data tools

FDA Drug Label

fda_drug_label

Official FDA label of a drug by brand or generic name: indications, dosage, warnings, boxed warning, contraindications, adverse reactions, interactions, pharmacologic class, manufacturer and NDC codes.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It says the label is 'official FDA' and lists content sections, but it omits behaviorally important details: whether the name match is exact or fuzzy, what happens with ambiguous names, whether multiple labels can be returned, and what the limit parameter does. For a lookup tool whose schema has an undocumented limit defaulting to 3, this is a meaningful gap.

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?

A single front-loaded sentence with the key identifier (drug name) stated early. The long enumeration of label sections is somewhat redundant because an output schema exists, but it remains compact and readable.

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?

The output schema covers return values, so the description needn't explain them. However, for a tool with no annotations and a 0%-documented schema, the description should explain the limit behavior and matching semantics to let an agent invoke it confidently; it does neither.

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?

Schema description coverage is 0%, so the description must compensate. It adds useful meaning for the name parameter ('brand or generic name'), but never mentions the limit parameter at all — neither its purpose nor its default of 3 — leaving half the parameters undocumented in both schema and description.

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+resource: retrieve the official FDA label for a drug by brand or generic name, and enumerates the label sections returned. It is clearly distinct from fda_recalls in practice, but the description never names or contrasts with that sibling, so it stops short of a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the sibling fda_recalls or clinical_trials. The only hint is 'by brand or generic name', which implies lookup flexibility but gives no conditions for choosing this tool.

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

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?