Query bilateral oil trade flows (EIA US imports/exports + Eurostat). Accepts structured filters OR a free-text query (matches country/notes). NOTE: this is import/export flow data, NOT chokepoint throughput — for Hormuz transit volumes use shipping_chokepoint.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | Free-text: a country name or keyword | |
| period | No | ||
| partner | No | ||
| product | No | ||
| reporter | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description clarifies this is import/export flow data, not chokepoint throughput, but does not disclose other behavioral traits like response format or data freshness.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences front-load the purpose and include critical usage guidance with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Handles 6 parameters with no output schema or annotations; description covers core purpose and key sibling differentiation but lacks details on output format, required context, or additional constraints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Adds meaning for 'query' parameter (free-text matching country/notes) but does not describe limit, period, partner, product, or reporter parameters, despite low schema coverage (17%).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it queries bilateral oil trade flows from specific sources (EIA, Eurostat) and explicitly distinguishes from chokepoint data by name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use (bilateral oil trade) and when not to (use shipping_chokepoint for Hormuz transit volumes), and mentions it accepts structured filters or free-text query.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but there is some overlap between shipping_status and shipping_freshness (both provide freshness information) and between shipping_sanctions and shipping_sanctioned_at_eu (both deal with sanctions, though one is general and the other EU-specific). Descriptions help disambiguate, but the potential for confusion remains.
All tools follow a consistent 'shipping_' prefix followed by a descriptive noun phrase (e.g., shipping_chokepoint, shipping_emissions, shipping_oil_trade). The naming pattern is uniform and predictable, with no mixed conventions.
With 13 tools, the server covers a broad domain (chokepoints, trade flows, emissions, fleet, sanctions, document intelligence, oil data) without being overwhelming. Each tool serves a clear, non-redundant purpose, and the count is well-scoped for a specialized maritime intelligence server.
The tool set covers core maritime intelligence areas: chokepoint monitoring, trade flows, emissions, fleet, sanctions, oil prices, and data freshness. Minor gaps exist (e.g., no tool for port congestion or vessel tracking outside chokepoints), but the core workflows for sanctions, trade, and emissions are well-covered.