Skip to main content
Glama

BRAINIAC FDA Drug Device and CQC Location Lookup

Look up FDA Orange Book products, patents and exclusivity

health-codes_fda-orange-book-lookup
Read-onlyIdempotent

Return Orange Book product, therapeutic-equivalence, patent and exclusivity rows for an application number, trade name or ingredient from the vendored Orange Book data files. Price $0.03 USDC. POST /api/v1/health-codes/fda-orange-book-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-orange-book-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
applNoNoapplNo, string. Optional.
applTypeNoapplType, string, one of N, A. Optional.
tradeNameNotradeName, string, length 1 to 200. Optional.
ingredientNoingredient, string, length 1 to 200. Optional.
includeDiscontinuedNoincludeDiscontinued, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
productsNoproducts. Array.
limitationsNolimitations. Array.
snapshotDateNosnapshotDate. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), but the description adds material context beyond them: a fixed $0.03 USDC price, the endpoint path, and the crucial failure mode that an unpaid call returns x402 payment terms and does not execute. It does not clarify whether at least one lookup key is required despite all parameters being formally optional, nor any rate limits.

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?

Three short sentences with the resource scope front-loaded, followed by cost, endpoint and the payment-failure behavior. No redundant restatement of the title and no filler.

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?

With an output schema present, the description needn't explain return values, and it correctly focuses on scope, price and the unpaid-call behavior. The one gap relevant to correct invocation is the optionality of the lookup keys, which is left ambiguous against a schema where every property is optional.

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 only the mapping of three parameter concepts to the returned row types; it says nothing about 'applType' (N vs A) or why 'includeDiscontinued' defaults to true, leaving those entirely to the schema.

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 uses a specific verb ('Return') plus the exact resource ('Orange Book product, therapeutic-equivalence, patent and exclusivity rows') and names the three lookup keys (application number, trade name, ingredient). The domain is unmistakably distinct from the sibling FDA tools (510k, drug shortage, NDC, enforcement), so an agent can route here without opening the schema.

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?

Usage is only implied: the agent can infer it should call this when it has an application number, trade name or ingredient for an Orange Book lookup. There is no explicit when-to-use/when-not-to-use statement, no mention of how to choose between the three key types, and no named alternative for overlapping needs (e.g. NDC lookup).

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