Skip to main content
Glama
cliwant

mcp-sam-gov

openfda_device_clearances

Read-only

Search FDA 510(k) medical device clearances by applicant, device name, product code, clearance type, K-number, or state. Retrieve clearance details, decision dates, and manufacturer information.

Instructions

Search openFDA 510(k) DEVICE CLEARANCES — FDA premarket-notification clearances for medical devices, with the applicant/manufacturer, device name, clearance number (K-number), decision (date + description), clearance type, product code, advisory committee, and geography (openFDA /device/510k.json; api.fda.gov). KEYLESS (optional free OPENFDA_API_KEY only raises the rate limit — keyless works at ~1000 requests/day; NEVER throws for a missing key). Input: STRUCTURED filters — applicant, deviceName, productCode, clearanceType (e.g. Traditional/Special/Abbreviated), kNumber (e.g. 'K123456'), state (2-letter) — safely escaped into the openFDA search= Lucene string (NO raw passthrough), plus limit (1..100, default 25) and skip (offset ≥0). Returns { clearances:[{ applicant, deviceName, kNumber, decisionDate, decisionDescription, clearanceType, productCode, advisoryCommittee, state }] } + honest _meta. HONESTY: totalAvailable is openFDA's EXACT meta.results.total (skip/limit pagination via hasMore/nextOffset — never results.length); every scalar is null-never-empty-string; decision_date is a YYYY-MM-DD string. ★A no-match query returns openFDA HTTP 404 → HONEST EMPTY (returned:0/total:0), NOT an error; 400 → invalid_input surfacing openFDA's message; 5xx → THROWS; 200 non-JSON → schema_drift. Optional key rides ONLY in &api_key= param.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoRow offset for pagination (default 0). Page with _meta.pagination.nextOffset.
limitNoMax clearance records to return (default 25, max 100). Offset-paginated via skip.
stateNo2-letter US state/territory postal code filter (→ state), e.g. 'CA'. Validated ^[A-Za-z]{2}$.
kNumberNo510(k) clearance number (K-number) filter (→ k_number), e.g. 'K123456'. Matched as an escaped Lucene phrase.
applicantNoApplicant / manufacturer name filter (→ applicant), e.g. 'medtronic'. Matched as an escaped Lucene phrase.
deviceNameNoDevice name filter (→ device_name), e.g. 'catheter'. Matched as an escaped Lucene phrase.
productCodeNoFDA product code filter (→ product_code), e.g. 'DXN'. Matched as an escaped Lucene phrase.
clearanceTypeNo510(k) clearance type filter (→ clearance_type), e.g. 'Traditional', 'Special', 'Abbreviated'. Matched as an escaped Lucene phrase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

A4.7/5.0
Behavior5/5

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

The description goes far beyond the readOnlyHint/openWorldHint annotations, disclosing exact semantics for totalAvailable, hasMore/nextOffset pagination, null handling, date formatting, and mappings of openFDA HTTP errors to honest empty, invalid_input, throws, and schema_drift. It also specifies where the API key rides. This is rich behavioral disclosure.

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?

Though long, every sentence carries distinct information: purpose, endpoint, parameters, return shape, and error behavior. It is front-loaded with the core function and endpoint, uses organized sections, and avoids repetition. No filler.

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?

With no output schema, the description supplies a full return structure (clearances array and _meta with pagination) and maps each parameter to its query field. It covers error handling, pagination, key usage, and validation. Nothing an agent needs to call it correctly is missing.

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 descriptions cover all 8 parameters (100% coverage), so the baseline is 3. The description adds value with concrete examples for each filter (e.g. 'K123456', 'DXN', 'Traditional/Special/Abbreviated') and clarifies the safe Lucene escaping behavior and pagination semantics, which are not in 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?

Description opens with a specific verb ('Search openFDA 510(k) DEVICE CLEARANCES') and names the resource, fields, and endpoint. It clearly distinguishes this from sibling FDA tools (openfda_drug_approvals, openfda_enforcement) by domain and data layout.

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 is unambiguous about what it does and includes operational notes (keyless mode, rate limits, API key behavior), giving clear context for when to call it. However, it never explicitly names sibling alternatives or states exclusions, so an agent must infer the boundary from the resource name.

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