Skip to main content
Glama

Compare tariff classifications

compare_tariff_codes
Read-onlyIdempotent

Access: API key required. Find edition-aware concordance candidates between China, US, EU, GB, and Brazil tariff systems. Supports historical as-of resolution, up to five targets, projections, and cursor pagination. Candidates are non-binding classification leads.

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": {
      "code": "<code>",
      "source": "<source>"
    },
    "name": "compare_tariff_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
as_ofNoISO date in YYYY-MM-DD form
limitNo
cursorNo
sourceYes
targetNo
includeNo
targetsNo
source_editionNo
target_editionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 context beyond them: API key authentication, cursor pagination, a five-target ceiling, historical as-of resolution, and the important caveat that results are non-binding leads rather than definitive rulings.

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?

Four tight sentences with the access prerequisite front-loaded and the substantive scope following immediately. Dense but not padded; every clause carries information, though 'projections' is an unexplained term that costs a little clarity.

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 10-parameter tool with no output schema and very thin schema descriptions, the definition covers the high-level shape (multi-target comparison, editions, pagination, non-binding results) but leaves key invocation details — notably the include options and the meaning of projections — undocumented anywhere. Adequate orientation, insufficient for confident parameterization.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 10% across 10 parameters, so the description carries most of the burden and largely fails to meet it. It hints at as_of ('historical as-of resolution'), targets ('up to five targets'), cursor, and edition-awareness (source_edition/target_edition), but says nothing about code, source, target, limit, or the include values (codes/hierarchy/measures), and 'projections' maps to no identifiable parameter.

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 gives a specific verb and resource — find concordance candidates between named tariff systems (China, US, EU, GB, Brazil) — which clearly separates it from a single-code lookup like lookup_tariff. It does not explicitly name a sibling it is not, but the 'candidates' framing and multi-jurisdiction scope make the function unambiguous.

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: 'concordance candidates' plus 'non-binding classification leads' tells an agent this is exploratory cross-classification, not an authoritative lookup. There is no explicit when-not-to-use guidance or routing to alternatives such as lookup_tariff or search_tariffs, and no prerequisite beyond the API key.

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