Skip to main content
Glama

List monitored tariff changes

list_tariff_changes
Read-onlyIdempotent

Access: Pro API key or higher required. List customer-scoped tariff changes with optional workflow and classification filters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tariff_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
htsNo
limitNo
beforeNo
originNoISO-2 country code of origin
before_idNo
acknowledgedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely useful context in the Pro API key prerequisite and the customer-scoping of results, which is not in the structured data. However, the "workflow and classification filters" phrasing introduces ambiguity, since no such parameters exist in the schema.

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?

At two sentences it is appropriately short and front-loads the access requirement. But the second sentence spends its limited budget on filter language that misaligns with the actual schema, so brevity comes at the cost of usefulness rather than from efficiency.

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

Completeness2/5

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

For a six-parameter listing tool with no output schema and very low schema coverage, the description leaves pagination (limit, before, before_id), ordering, and the meaning of acknowledged undefined. An agent cannot reliably construct a paging loop or interpret the response from this text alone.

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 17% across six parameters (hts, limit, before, before_id, acknowledged, origin), so the description needs to compensate and does not. Worse, the filters it does mention, "workflow" and "classification," do not map cleanly onto any parameter name, leaving an agent to guess that classification means hts and workflow means acknowledged.

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?

"List customer-scoped tariff changes" gives a specific verb and resource plus a scope qualifier (customer-scoped) that separates it from the lookup/comparison siblings. It stops short of naming an alternative tool or clarifying how it differs from search_tariffs or replay_tariff.

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

Usage Guidelines2/5

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

The only usage-adjacent content is "optional workflow and classification filters," with no statement of when to choose this tool over siblings like search_tariffs or lookup_tariff. There are no exclusions, no preconditions beyond the API tier, and no scenario examples.

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