Skip to main content
Glama

BRAINIAC FDA Drug Device and CQC Location Lookup

Look up an FDA NDC product or package

health-codes_fda-ndc-lookup
Read-onlyIdempotent

Resolve a 10-digit or 11-digit NDC, or search a proprietary/non-proprietary name, in the vendored FDA NDC Directory subset of human prescription and OTC drugs. Price $0.03 USDC. POST /api/v1/health-codes/fda-ndc-lookup. An unpaid call returns the x402 payment terms and does not run.

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": "health-codes_fda-ndc-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
ndcNondc, string. Optional.
nameNoname, string, length 2 to 120. Optional.
limitNolimit, integer, from 1 to 50. Required.
labelerNolabeler, string, length 1 to 200. Optional.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
snapshotDateNosnapshotDate. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the description is not the main source of safety information. It still adds genuinely useful behavior the annotations cannot express: the $0.03 USDC price and the fact that an unpaid call returns x402 payment terms without executing, which changes how an agent should retry after a failure.

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?

Three short sentences, front-loaded with the capability, then cost, then endpoint, then the payment failure mode. Little waste, though the raw endpoint string is arguably redundant with the tool name.

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?

An output schema exists so return values need not be explained, and the description covers the two ways in (NDC or name) plus the payment gate. Remaining gaps, mainly how 'labeler' interacts with name and whether ndc and name are mutually exclusive or combined, are small for a lookup tool.

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 baseline is 3. The description adds modest meaning beyond the schema by stating the NDC must be 10 or 11 digits (the schema pattern allows 9-13 characters) and that name matching covers proprietary and non-proprietary names, but says nothing about 'labeler' or 'limit'.

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 specific verbs and the resource precisely: 'Resolve a 10-digit or 11-digit NDC, or search a proprietary/non-proprietary name' in the 'vendored FDA NDC Directory subset of human prescription and OTC drugs'. That scope distinguishes it from the 510(k), Orange Book, shortage and enforcement siblings by resource rather than by naming them, so it is clear but does not explicitly route against siblings.

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?

Implies when to use it (you have an NDC or a drug name and want directory data) and notes the payment precondition, but gives no when-not-to-use guidance and never points to the enforcement, shortage, or Orange Book tools for the adjacent questions an agent would actually have.

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