Skip to main content
Glama

Triplicate – export documents

Search Triplicate trade guides

search_trade_guides
Read-only

Use when a user asks an export or import rules question (documents, registration, labelling, duties, origin, Incoterms, letters of credit) and wants a source to read; the user confirms the rule with the authority or a customs broker. Search Triplicate's practical trade guides (over 250 notes in 15 languages, checked against official sources: export guides for about 50 countries, import registration, labelling and product certification by country, cosmetics and food rules, US tariffs and refunds, EORI, rules of origin and certificates of origin, HS classification, Incoterms, letters of credit, bills of lading, dangerous goods, invoices and packing lists) and tool guides. Returns titles, page links and excerpts to cite.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesQuestion or topic in any of the 15 site languages, e.g. 'EORI number for UK imports', 'sheet mask HS code', 'CIF insurance 110%'
languageNoOptional: language of the guides to search (detected from the query otherwise)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the description's job is to add context beyond safety — and it does: corpus size (250+ notes, 15 languages, checked against official sources) and result shape ('titles, page links and excerpts to cite'). It also flags the non-authoritative nature of the output, which is genuinely useful. It says nothing about result limits, ranking, or behavior on empty results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Correctly front-loaded with the 'Use when' trigger, but the middle is a single run-on sentence containing a 15-item parenthetical catalogue that is far longer than needed for selection. The core signal could be delivered in half the text; the exhaustive topic list reads as marketing copy.

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 compensates by stating what is returned (titles, links, excerpts), the corpus scope and multilingual coverage. An agent can call this confidently; only the limit parameter's behavior and result ordering remain unaddressed.

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 67%: query and language are documented in the schema (with a language enum), so the description doesn't need to repeat them. However, the 'limit' parameter has no schema description and no mention here — the agent must guess whether it caps result count or something else. Marginal value added over 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?

States a specific verb and resource ('Search Triplicate's practical trade guides') and enumerates the covered domains, so an agent knows exactly what corpus is being queried. Sibling differentiation is only implicit, though: the topic list overlaps lookup_hs_code and read_letter_of_credit without saying whether this tool complements or replaces them.

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

Usage Guidelines4/5

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

'Use when a user asks an export or import rules question ... and wants a source to read' gives a clear triggering condition, and the clause about confirming with the authority or a customs broker sets an important expectation about authority. No explicit exclusions or named alternatives are given, which keeps it short of a 5.

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