Skip to main content
Glama
Sign In
OpenFDA

OpenFDA

by ythalorossy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-drug-by-product-ndc

Retrieve comprehensive drug information using a product NDC code in XXXXX-XXXX format. This tool finds all package variations for a specific pharmaceutical product from the OpenFDA database.

Instructions

Get drug information by product NDC only (XXXXX-XXXX format). This ignores package variations and finds all packages for a product.

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": {
      "productNDC": "<productNDC>"
    },
    "name": "get-drug-by-product-ndc"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNDCYesProduct NDC in format XXXXX-XXXX

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does operationally. It doesn't disclose behavioral traits like whether this is a read-only operation, what format the drug information returns, error handling, rate limits, or authentication requirements for a tool that accesses drug data.

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 extremely concise with just two sentences that are front-loaded with the core purpose. Every word earns its place - the first sentence states what the tool does, and the second clarifies its scope and behavior.

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 simple lookup tool with 100% schema coverage but no annotations or output schema, the description adequately covers the basic operation. However, it doesn't address what 'drug information' includes, the response format, or potential limitations - gaps that become more significant without structured output documentation.

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 schema already documents the single parameter's format. The description reinforces the format requirement but doesn't add meaningful semantic context beyond what the schema provides, such as examples of valid NDCs or what constitutes a 'product' versus 'package' NDC.

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 clearly states the specific verb ('Get drug information') and resource ('by product NDC'), and explicitly distinguishes from sibling tools by specifying it uses product NDC format and ignores package variations (unlike 'get-drug-by-ndc' which likely handles package-level NDCs).

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?

The description provides clear context about when to use this tool ('by product NDC only') and what it does ('ignores package variations and finds all packages for a product'), but doesn't explicitly mention when NOT to use it or name specific alternatives among the sibling tools.

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