Skip to main content
Glama

Check a list of suppliers

check_supplier_list
Read-onlyIdempotent

Up to 20 suppliers checked at once against FDA's records: for each, the firm matched (or several to choose from by address, or none found under that name), what FDA has on record and its page.

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

Input Schema

NameRequiredDescriptionDefault
suppliersYes

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 declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds behavior annotations don't carry: the 20-item cap, the three possible per-supplier outcomes (one match, multiple matches to disambiguate by address, or no match under that name), and that a record page is returned.

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?

A single front-loaded sentence with the batch limit first and the outcome taxonomy after; no filler. The nested parenthetical is dense and slightly awkward to parse, but every clause carries information.

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?

For a one-parameter, read-only lookup with no output schema, the description covers the essentials: scale limit, per-item result possibilities, and that a record page is returned. The remaining ambiguity — what 'page' refers to (URL vs. identifier) and how to resolve multi-match cases — is minor.

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 reported as 0%, so the description must compensate; it partially does by conveying that supplier identity is name-based with address used to disambiguate between plants, and by restating the 20-item cap. It adds nothing about name formatting, country code acceptability, or what happens when a name is ambiguous beyond 'several to choose from'.

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?

States a specific verb and resource (check suppliers against FDA's records) plus the batch scope of up to 20 at once. The return shape per supplier (single firm match, several to choose from, or none found) further separates it from single-record siblings like get_supplier_record, 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?

Batch semantics ('Up to 20 suppliers checked at once') imply the right context — bulk verification rather than one-off lookups — but there is no explicit when-to-use/when-not statement and no mention of when to prefer search_suppliers or get_supplier_record instead.

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