Skip to main content
Glama
Sign In

Gateway Lines Tariff

by com.gatewaylines
OverviewDiscussionsAdmin

List US trade policy changes

policy_changes_since
Read-onlyIdempotent

List US trade policy changes Gateway has published since a given date: new tariff actions, rate changes, effective dates and expirations, each with its official source. Also returns, under upcoming, earlier entries for changes announced or proposed but not yet in force. Use to answer "what changed recently" or "what is coming". Not charged: it does not use a duty lookup.

Input Schema

NameRequiredDescriptionDefault
limitNoMax entries to return, default 10, max 50.
sinceNoISO date, e.g. "2026-07-01". Filters on when Gateway PUBLISHED the change. Defaults to 30 days ago.

Output Schema

NameRequiredDescriptionDefault
countNo
sinceNoThe date filtered on, ISO.
sourceNo
changesNo
gatewayNo
upcomingNoEntries published BEFORE `since` that are still pending or monitoring, newest first, so "what is coming" is answerable whatever date is asked about.
disclaimerNo
guest_allowanceNo
guest_lookups_remainingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max entries to return, default 20, max 50."New value: +"Max entries to return, default 10, max 50."
    • addedOutput schema / properties / changes / items / properties / affects
      Added value: +{
+  "description": "The products or goods affected.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / changes / items / properties / impact / description
      Added value: +"Gateway's risk rating for importers."
    • addedOutput schema / properties / changes / items / properties / policy_type / description
      Added value: +"The trade authority, e.g. Section 232 or Section 301."
    • addedOutput schema / properties / changes / items / properties / source_name
      Added value: +{
+  "description": "The official source, e.g. a Federal Register document or CBP CSMS message.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / changes / items / properties / source_url
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / changes / items / properties / status / description
      Added value: +"implemented (in force), pending (announced, not yet in force), monitoring (proposed or under review), suspended, removed, reaffirmed or new."
    • addedOutput schema / properties / guest_allowance
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / upcoming
      Added value: +{
+  "description": "Entries published BEFORE `since` that are still pending or monitoring, newest first, so \"what is coming\" is answerable whatever date is asked about.",
+  "items": {
+    "properties": {
+      "affects": {
+        "description": "The products or goods affected.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "countries": {
+        "type": [
+          "string",
+          "array",
+          "null"
+        ]
+      },
+      "effective": {
+        "description": "Free text as published, e.g. \"In effect for goods entered on or after...\". Not a date and not parseable as one.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "impact": {
+        "description": "Gateway's risk rating for importers.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "policy_type": {
+        "description": "The trade authority, e.g. Section 232 or Section 301.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "published": {
+        "description": "When Gateway published the entry. This is what `since` filters on.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "source_name": {
+        "description": "The official source, e.g. a Federal Register document or CBP CSMS message.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "source_url": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "status": {
+        "description": "implemented (in force), pending (announced, not yet in force), monitoring (proposed or under review), suspended, removed, reaffirmed or new.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "title": {
+        "type": "string"
+      },
+      "what_changed": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already carry readOnly/idempotent/non-destructive/openWorld, so the description needn't restate safety. It adds genuinely new behavior: a separate "upcoming" block containing entries announced or proposed but not yet in force (so results include non-effective items), sourcing per entry, and a cost note ("Not charged"). It stops short of describing volume/pagination behavior beyond limit.

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

Conciseness5/5

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

Three tight sentences with the purpose and scope front-loaded, followed by the non-obvious "upcoming" behavior and the cost/boundary note. No filler or restatement of the title.

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?

Output schema exists so return formatting needn't be explained, and the description still flags the non-obvious shape of the result (an "upcoming" group separate from in-force changes). Parameters, usage triggers, cost, and sibling boundary are all covered for a simple two-optional-param read tool.

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 100% and both parameters are documented there, including default 30 days and max 50. The description reinforces that "since" filters on Gateway's PUBLISH date rather than effective date, but that distinction already appears in the schema, so it adds little beyond the baseline.

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 and resource ("List US trade policy changes") plus the scope constraint ("since a given date") and enumerates exactly what each entry contains: tariff actions, rate changes, effective dates/expirations, official source. The closing "does not use a duty lookup" separates it from the duty-oriented siblings landed_cost and classify_hts.

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 two concrete question shapes it answers ("what changed recently", "what is coming") and signals the sibling boundary by noting it does not perform a duty lookup, pointing agents to the cost/HTS tools for that need. No inference is required to select it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gateway Lines Tariff toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources