Skip to main content
Glama
Sign In
Globalpulse-MCP

Globalpulse-MCP

by gpavan1992
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UN Comtrade — Bilateral Trade Flows

globalpulse_trade_get_bilateral_flows
Read-onlyIdempotent

Retrieve bilateral trade flows (imports and exports) between country pairs using UN Comtrade data, filtered by year, commodity code, and flow direction.

Instructions

Bilateral trade data from UN Comtrade. Imports, exports by country pair and HS commodity code. Common HS codes: TOTAL (all), "27" (oil/fuel), "84" (machinery), "85" (electronics), "87" (vehicles), "30" (pharma), "10" (cereals). Args: reporter, partner (default "world"), year (2000-2023), flow ("all","X","M"), commodity_code, limit, response_format

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": {
      "reporter": "<reporter>"
    },
    "name": "globalpulse_trade_get_bilateral_flows"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowNoall
yearNo
limitNo
partnerNoworld
reporterYes
commodity_codeNoTOTAL
response_formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description's burden is lower. It adds that the data comes from UN Comtrade and involves HS codes, but no additional behavioral details (e.g., rate limits, pagination, data freshness) are provided.

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?

The description is two sentences plus a compact argument list, front-loading the core purpose and examples. No wasted words; every element serves a purpose.

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?

The description covers parameters well but lacks details on the response format beyond the 'response_format' parameter. Without an output schema, more context on the returned data structure (e.g., columns, pagination) would be beneficial for a data retrieval tool.

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 0%, so the description must compensate. It lists all seven arguments with defaults and valid ranges (e.g., year 2000-2023, flow enums, common HS codes). Missing explanation of what 'reporter' and 'partner' accept (e.g., country names vs. codes), but the provided info is largely sufficient.

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?

Description clearly states it returns bilateral trade data from UN Comtrade, with imports/exports by country pair and HS commodity code. The title and first sentence make the purpose unmistakable, and no sibling tools overlap in functionality.

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?

Description provides useful examples of common HS codes but does not explicitly state when to use or avoid this tool versus alternatives. There are no sibling trade tools, so implied usage is clear, but the lack of explicit guidance on prerequisites or contexts limits the score.

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

Deploy Server

Other Tools