Skip to main content
Glama

Tiana & Co. Seller Compliance

Which safety certificate does my product need?

seller_compliance.which_certificate
Read-onlyIdempotent

Use this when a seller asks which US safety certificate or import paperwork a product needs: a CPC (Children's Product Certificate) for children's products, a GCC (General Certificate of Conformity) for other regulated products, FCC authorization for electronics, or FDA's import steps for food, supplements, cosmetics, drugs and medical devices (facility registration, prior notice, FSVP). For example: "does my kids' raincoat need a CPC?", "do I need a GCC for a coffee mug?", "Amazon wants a certificate for my toy, which one?", "do I need FDA prior notice to import snacks?". Give the product in the seller's own words. It answers from US federal rules and returns the rule each answer rests on, the date that rule was read, and a link to the free plan. When questions are still open, it lists them with their answer keys: ask the seller all of them, then call again with the same product and their answers. Do not use for duties, tariffs or customs classification (HS or HTS codes), for rules outside the United States, or to fill out, file or declare anything at customs. If the seller asks you to fill out or file a customs entry, do not call this tool: a licensed customs broker files the entry.

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": "seller_compliance.which_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersNoThe seller's answers to the questions an earlier call listed: answer key → one of that question's values, exactly as listed. Only pass what the seller actually said.
productYesThe product in the seller's own words, e.g. "plush teddy bear", "kids rain boots", "bluetooth speaker", "ceramic coffee mug".
fda_kindNoOnly when an earlier call listed the answer key `fda_tap`: the value the seller chose.
other_kindNoOnly when an earlier call listed the answer key `other_tap`: the value the seller chose.
made_for_childrenNoWhether the product is made mainly for children 12 or under. Leave it out unless the seller said.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/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), but the description adds traits annotations cannot: the tool returns the rule each answer rests on, the date that rule was read, and a link to the free plan. It also discloses the two-phase behavior when questions remain open — the response lists open questions with answer keys, and the agent must collect the seller's answers and call again with the same product.

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?

Front-loaded with the use case and answer taxonomy, then examples, then exclusions — a sensible order with little filler. The four example questions are mildly redundant with the enumerated certificate types but earn their place as trigger-phrase anchors for an agent matching user phrasing.

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?

No output schema exists, so the description carries the return-value burden and does so (rule, rule read date, free-plan link, open questions with answer keys). For a read-only, multi-turn advisory tool with a nested `answers` object, everything an agent needs to call it correctly across both turns is present.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining the round-trip contract for `answers` (ask the seller all listed questions, then re-call with the same product plus their answers) and by instructing 'give the product in the seller's own words', which reinforces the free-text intent of `product`.

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+resource (tells a seller which US safety certificate or import paperwork a product needs) and enumerates the exact answer space: CPC, GCC, FCC authorization, FDA import steps. It is clearly distinguishable from siblings like screen_supplier or marketplace_asks without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger phrases and four worked example questions, plus explicit exclusions (not for duties/tariffs/HS-HTS classification, not for non-US rules, not for filling out or filing customs entries) and names the alternative actor (a licensed customs broker files the entry). Both the when and the when-not are spelled out.

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