Skip to main content
Glama

FDA GUDID device record by Device Identifier: brand

health_fda_device_gudid
Read-only

FDA GUDID device record by Device Identifier (DI, the GS1/GUDID number on a device label): brand, company, model, description, GMDN term, MRI safety status, single-use and prescription flags. From openFDA's GUDID copy, with FDA AccessGUDID as fallback. Lookup by DI only; no name search. Related tools on this server, for a different need: health_fda_medical_device_510k when you need FDA 510 premarket notifications: K-number, device name; health_fda_adverse_events_faers when you need FDA FAERS drug adverse event reports for a generic drug. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
diYesDevice Identifier, 8 to 14 digits

Output Schema

NameRequiredDescriptionDefault
diNo
rxNo
urlNo
sourceNo
gmdnTermNo
brandNameNo
checkedAtNo
mriSafetyNo
singleUseNo
companyNameNo
descriptionNo
modelNumberNo
publishDateNo
catalogNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing data provenance (openFDA's GUDID copy with FDA AccessGUDID as fallback) and the exact billing behavior ($0.002 per successful call via x402, failed calls not charged). Those are operational facts an agent cannot infer from annotations or schema.

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?

Front-loaded with the resource and return fields, followed by scope, alternatives and price — a logical order with no filler sentences. It is dense and the pricing/network boilerplate is long, but each clause carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with a full output schema, annotations covering safety, and explicit provenance and pricing, nothing needed to call it correctly is missing. Return values are delegated to the output schema rather than redundantly restated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already specifies '8 to 14 digits', so the baseline is 3; the description adds meaning by glossing DI as 'the GS1/GUDID number on a device label', which tells the agent where to find the value. It does not add format or validation detail beyond that.

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+resource ('FDA GUDID device record by Device Identifier') and enumerates the returned fields (brand, company, model, GMDN term, MRI safety status, single-use and prescription flags). It also explicitly scopes the lookup to DI and names sibling tools (health_fda_medical_device_510k, health_fda_adverse_events_faers) with the need each one serves, so an agent can route without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the selection constraint ('Lookup by DI only; no name search') and gives the condition that selects each named alternative ('when you need FDA 510 premarket notifications', 'when you need FDA FAERS drug adverse event reports'). This is when-to-use plus exclusion guidance, not just context.

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