Skip to main content
Glama

Check paperwork fit

check_fit
Read-only

Who lists the paperwork each US rule for a product asks for. Checks every supplier selling the product (counts per rule), plus up to 10 named suppliers and the others that list the most, in detail: which list a matching certificate, which only claim it in a product listing, which have only a foreign mark or a lab name; and which rules are the importer's own job. Spends one search.

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

Input Schema

NameRequiredDescriptionDefault
refsNoSupplier refs (E1234) from search_listings to check in detail. Leave out to check the ones that list the most.
productYesProduct words, e.g. 'bamboo cutting board'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / refs / description
      Previous value: -"Exhibitor refs (E1234) from search_listings to check in detail. Leave out to check the ones that list the most."New value: +"Supplier refs (E1234) from search_listings to check in detail. Leave out to check the ones that list the most."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description need not restate safety. It adds genuinely useful behavior: coverage is exhaustive at the count level (every supplier selling the product), detail is capped at 10 named suppliers plus top listers, results are classified into certificate / listing-claim / foreign-mark-or-lab-name / importer's-own-rule, and the call consumes one search credit. It does not clarify failure modes or what happens with zero matches.

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?

Two dense sentences with no filler, and the coverage/cost facts are front-loaded rather than buried. The first sentence is syntactically tangled and requires re-reading, which costs it a point, but nothing is redundant.

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

Completeness3/5

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

For a read-only two-parameter tool with full schema coverage and no output schema, the description should convey the shape of the answer, and it does so at a category level (per-rule counts plus per-supplier classification and importer-obligation flags). It stops short of describing how results are organized or returned, leaving an agent unsure what it will actually receive.

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 100%, so both parameters are already documented, including the E1234 ref format and the default-to-top-listers behavior when refs are omitted. The description reinforces the two-tier behavior (counts for all suppliers, depth for named/top ones) but adds no syntax, limits, or format details beyond the schema, so the baseline of 3 applies.

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 makes the specific operation clear: it evaluates which suppliers list the paperwork that each US rule for a product requires, with per-rule counts and supplier-level detail. That distinguishes it from us_requirements (which presumably lists the rules) and from get_suppliers/search_listings, though it never names those siblings explicitly and the opening clause ("Who lists the paperwork each US rule for a product asks for") is grammatically awkward.

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 only implied: the tool is evidently for compliance/paperwork gap checks on a product's suppliers, and "Spends one search" signals a cost budget. There is no explicit when-to-use guidance, no statement of when to prefer us_requirements or get_suppliers instead, and no prerequisites (e.g. that refs must come from search_listings, which appears only in the schema).

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