Skip to main content
Glama

Find a supplier in FDA records

search_suppliers
Read-onlyIdempotent

Firms in the U.S. FDA's food records whose name matches, best first, each with its country, city, FDA establishment number (FEI), counts of FDA actions and its Supplier Brief page. Also finds a firm by its FEI number.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe supplier's name as on its invoice, or its FEI number.
countryNoThe supplier's country: a name such as 'India' or a two-letter code such as 'IN'.

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 declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: results are ranked best-first, and lookup works both by name string and by FEI number. It stops short of describing pagination, result limits, or no-match behavior.

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?

Two sentences, zero filler, with the primary search behavior front-loaded and the FEI variant relegated to a short secondary clause. The return-field enumeration is dense but earns its place given there is no output schema.

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 no output schema, the description correctly carries the burden of explaining what comes back, listing the fields per firm. The main residual gap is the undocumented optional 'country' filter and no-match semantics, which matter for a search tool with two parameters.

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%, so the schema already documents both parameters, including that 'name' accepts an FEI number. The description reinforces the dual name/FEI mode but says nothing about the optional 'country' parameter — when to supply it or how it narrows results — so it adds little beyond 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?

States a specific verb and resource: firms in the FDA's food records matched by name, ranked best first, plus FEI lookup. It enumerates exactly what each result carries (country, city, FEI, action counts, Supplier Brief page), so an agent knows the shape of the answer before calling.

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 implied rather than stated: search when you have a name or FEI number. It does not say when to prefer this over the sibling get_supplier_record or check_supplier_list, nor does it state what to do when no match is found or when results are ambiguous.

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