Skip to main content
Glama

BRAINIAC FDA Drug Device and CQC Location Lookup

Look up an FDA 510(k) or De Novo decision

health-codes_fda-510k-lookup
Read-onlyIdempotent

Find a 510(k) or De Novo decision by number, applicant, device name or product code in the vendored FDA 510(k) releasable database (1996–current). Price $0.03 USDC. POST /api/v1/health-codes/fda-510k-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-510k-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer, from 1 to 50. Required.
kNumberNokNumber, string. Optional.
applicantNoapplicant, string, length 2 to 200. Optional.
deviceNameNodeviceName, string, length 2 to 200. Optional.
productCodeNoproductCode, string. Optional.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely non-derivable behavior: the data is vendored with 1996–current coverage, each call costs $0.03 USDC, and an unpaid call short-circuits to payment terms rather than running. It omits that all five parameters are optional, so a bare call could return a broad unfiltered dump.

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 tight sentences, front-loaded with the lookup capability and then the operational facts (price, endpoint, payment gating). Nothing is padded, though the endpoint path and price are somewhat mechanical and partly echo the title.

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 no explanation, and the payment gating plus data vintage are the two facts an agent could not infer elsewhere. The remaining gap is that the description never says whether any filter is mandatory or what happens to an unfiltered call beyond returning up to the limit.

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 kNumber's pattern, applicant/deviceName lengths, productCode's format, and limit's 1–50 range. The description's listing of the four lookup keys adds only light framing about them being alternative identifiers, and it never mentions the pagination parameter. Baseline 3 applies.

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?

States a specific verb and resource ('Find a 510(k) or De Novo decision') plus the exact identifier set (number, applicant, device name, product code) and the underlying data source with its temporal coverage. That is enough to separate it from the four sibling lookups (drug shortage, NDC, Orange Book, CQC, drug enforcement) without opening a schema.

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 makes the usage model clear: you search a vendored FDA database by any of four identifiers, and an unpaid call returns x402 payment terms and does not execute. It never states when to prefer this over a sibling or whether at least one filter is required, but the invocation context is unambiguous.

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