Skip to main content
Glama
Sign In

Trade Intel

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Trade Macro Dashboard

trade_macro_dashboard
Read-onlyIdempotent

Check US trade indicators: monthly customs duty revenue, Treasury exchange rates, import/export price indices, maritime port disruptions, and the FRED macro block (trade-weighted dollar index, goods-and-services balance, imports, exports). Bilateral figures are NOT here — for one country's trade balance or monthly trend, call census_trade_balance or census_trade_trends with a country.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_fredKey": "your-trade-intel-api-key"
    },
    "name": "trade_macro_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
_blsKeyNoBLS registration key (gateway-injected; without it the price-index subcall runs keyless against a 25/day-per-IP cap)
_fredKeyNoFRED API key (gateway-injected, for the macro series)

Output Schema

NameRequiredDescriptionDefault
analysisYesAnalysis type identifier
fred_macroNoFRED macro series if API key provided
trade_trendsYes12-month trade trends from Census
price_indicesYesBLS import/export price indices
trade_balanceYesUS trade balance from Census
exchange_ratesYesExchange rates from Treasury
customs_revenueYesUS customs revenue from Treasury

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / _blsKey
      Added value: +{
+  "description": "BLS registration key (gateway-injected; without it the price-index subcall runs keyless against a 25/day-per-IP cap)",
+  "type": "string"
+}
    • changedInput schema / properties / _fredKey / description
      Previous value: -"FRED API key (optional, for macro series)"New value: +"FRED API key (gateway-injected, for the macro series)"
  2. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "analysis",
-  "customs_revenue",
-  "exchange_rates",
-  "trade_balance",
-  "trade_trends",
-  "fred_macro",
-  "price_indices"
-]New value: +[
+  "analysis",
+  "customs_revenue",
+  "exchange_rates",
+  "trade_balance",
+  "trade_trends",
+  "price_indices"
+]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "analysis": {
+      "description": "Analysis type identifier",
+      "type": "string"
+    },
+    "customs_revenue": {
+      "description": "US customs revenue from Treasury",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "exchange_rates": {
+      "description": "Exchange rates from Treasury",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "fred_macro": {
+      "description": "FRED macro series if API key provided",
+      "properties": {
+        "dollar_index": {
+          "description": "Trade-weighted dollar index (DTWEXBGS)",
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "exports_goods_services": {
+          "description": "Exports of goods and services (EXPGS)",
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "goods_services_balance": {
+          "description": "Goods and services balance (BOPGSTB)",
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "imports_goods_services": {
+          "description": "Imports of goods and services (IMPGS)",
+          "type": [
+            "object",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "price_indices": {
+      "description": "BLS import/export price indices",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "trade_balance": {
+      "description": "US trade balance from Census",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "trade_trends": {
+      "description": "12-month trade trends from Census",
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "analysis",
+    "customs_revenue",
+    "exchange_rates",
+    "trade_balance",
+    "trade_trends",
+    "fred_macro",
+    "price_indices"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_fredKey": "your-trade-intel-api-key"
+  }
+]
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by listing the data blocks included and explicitly guaranteeing that bilateral figures are absent. It does not mention rate limits, but the _blsKey parameter description in the schema covers the keyless cap, so the gap is minor.

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?

Two sentences with zero filler. The first sentence front-loads the dashboard's scope and contents; the second sentence explicitly excludes bilateral data and points to alternatives. Every clause contributes meaningful information.

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?

With no required parameters, an output schema present, and annotations covering safety and open-world behavior, the description fully orients an agent: what the tool covers, what it does not cover, and which alternative tool to use. No critical information is missing for correct invocation.

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%, with both _fredKey and _blsKey adequately described as gateway-injected keys with explanations of their purpose. The tool description itself does not need to add parameter-level detail; the baseline score of 3 applies.

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?

The description names a specific action ('Check') and a specific resource ('US trade indicators'), enumerating the exact series covered (customs duty revenue, Treasury exchange rates, import/export price indices, maritime port disruptions, FRED macro block). It also explicitly states what is not included ('Bilateral figures are NOT here'), clearly distinguishing it from related trade tools.

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?

The description provides explicit context for when to use this tool (US aggregate trade indicators) and when not to use it (bilateral trade figures), naming the exact alternative tools to call instead: census_trade_balance or census_trade_trends. This leaves no ambiguity about selection.

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

All Trade Intel 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