Skip to main content
Glama

A supplier's FDA record

get_supplier_record
Read-onlyIdempotent

Everything FDA's public records show about one firm, dated: the FSVP compliance facts (import alert listings, refusals with FDA's charges, inspection classifications including OAI, compliance actions, warning letters, recalls), the latest records of each kind with FDA's reference, similar records considered and not counted, the page and the free PDF report.

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": {
      "supplier": "<supplier>"
    },
    "name": "get_supplier_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
supplierYesThe supplier's id (as search results give it), its FEI number, or its Supplier Brief page address.

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 the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not carrying that burden. It does add genuine behavioral context: records are dated, only the latest of each kind is returned with FDA's reference, records considered but not counted are surfaced, and a page plus free PDF report come back. It does not describe format or pagination, which keeps it from a 5.

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?

One front-loaded sentence that leads with what the tool returns and then unpacks the record categories. It is long and runs as a comma-separated list, but every clause names substantive content rather than 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?

There is no output schema, so the description must describe the return payload, and it does so in concrete detail, including the 'considered and not counted' nuance and the PDF artifact. What remains thin is guidance on identifier choice and on empty results, a minor gap for a single-parameter read 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 coverage is 100% and the single parameter already documents that it accepts a supplier id, FEI number, or Supplier Brief page address. The description adds no meaning beyond that; the ambiguity of which identifier form to prefer is left to the schema.

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?

The description names a specific resource (one firm's FDA public record) and enumerates its contents: FSVP compliance facts, import alerts, refusals, inspection classifications, warning letters, recalls. The phrase 'one firm' distinguishes it in scope from list-oriented siblings such as check_supplier_list, though no sibling is named explicitly.

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?

Use is only implied via scope language ('one firm' versus the list-style tools suggested by the sibling names). There is no explicit statement of when to pick this over check_supplier_list or search_suppliers, and no statement about prerequisites or when the tool returns nothing.

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