Skip to main content
Glama

Trade Intel

by io.github.pipeworx-io
OverviewAdmin

Trade Country Profile

trade_country_profile
Read-onlyIdempotent

Get a country's trade snapshot: top 10 import/export partners and top 10 commodities. Use country codes (e.g., 842 for US, 156 for China, 276 for Germany, 392 for Japan, 826 for UK).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoTrade year (default: last year)
country_codeYesCountry code (e.g., "842" for US)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesTrade year analyzed
analysisYesAnalysis type identifier
country_codeYesCountry code analyzed
top_export_partnersYesTop 10 export partner countries
top_import_partnersYesTop 10 import partner countries
top_export_commoditiesYesTop 10 exported commodities
top_import_commoditiesYesTop 10 imported commodities

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "analysis": {
+      "description": "Analysis type identifier",
+      "type": "string"
+    },
+    "country_code": {
+      "description": "Country code analyzed",
+      "type": "string"
+    },
+    "top_export_commodities": {
+      "description": "Top 10 exported commodities",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "top_export_partners": {
+      "description": "Top 10 export partner countries",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "top_import_commodities": {
+      "description": "Top 10 imported commodities",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "top_import_partners": {
+      "description": "Top 10 import partner countries",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "year": {
+      "description": "Trade year analyzed",
+      "type": "string"
+    }
+  },
+  "required": [
+    "analysis",
+    "country_code",
+    "year",
+    "top_import_partners",
+    "top_export_partners",
+    "top_import_commodities",
+    "top_export_commodities"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country_code": "842"
+  },
+  {
+    "country_code": "156",
+    "year": "2023"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the description's role is reduced. It adds that the tool returns top 10 partners and commodities, but does not disclose additional behavioral traits like data freshness or pagination. This is adequate but not beyond what annotations imply.

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 examples, no extraneous text. The core action and parameters are front-loaded, making it easy to scan.

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?

Given the simple parameter set (2 params, no enums, no nested objects) and the presence of an output schema, the description fully explains what the tool does and what it returns. No gaps remain for a standard use case.

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

Parameters4/5

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

Schema description coverage is 100%, with both 'year' and 'country_code' described. The description adds value by listing example country codes and clarifying the output's structure (top 10 partners/commodities), which goes beyond the schema to aid selection and interpretation.

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 clearly states the tool retrieves a country's trade snapshot, specifically the top 10 import/export partners and top 10 commodities. It distinguishes itself from sibling tools like 'trade_bilateral_analysis' and 'trade_macro_dashboard' by focusing on a concise snapshot.

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?

The description provides examples of country codes and notes the optional year parameter with a default, guiding use. It lacks explicit contrast with alternative trade tools, but the 'snapshot' phrasing implies a quick overview, which is sufficient context.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources