Skip to main content
Glama

supply-chain-intelligence

by io.github.SupplyMaven-SCR

get_chokepoint_traffic

Monitor real-time vessel traffic and congestion at critical maritime chokepoints — Suez Canal, Panama Canal, Strait of Malacca, Strait of Hormuz, Bab el-Mandeb, and other strategic waterways. Returns total vessel count, average speed, count of slow or stationary vessels, and a congestion score with severity level. When chokepoints congest or close, global shipping routes reroute within days — this data detects that signal in real time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the specific return fields (vessel count, average speed, slow/stationary count, congestion score) and explains the real-time signal. It lacks operational caveats (e.g., update frequency), but for a no-parameter read-only tool, it is reasonably transparent.

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 three sentences: purpose and scope, return values, and domain significance. Every sentence adds value, is front-loaded, and avoids fluff. It is concise yet informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description explains what the tool returns and why it matters, including the rerouting signal. It does not detail the exact units or time coverage, but for a simple snapshot tool with no output schema, it is sufficiently complete.

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?

The tool has zero parameters, so the baseline is 4. The description does not need to elaborate on parameter syntax or meaning; it instead focuses on the output, which is appropriate.

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 monitors real-time vessel traffic and congestion at critical maritime chokepoints, listing specific examples (Suez, Panama, Malacca, etc.). This specific verb-resource pairing distinguishes it from general port congestion tools and other siblings.

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 a clear use case: detecting chokepoint congestion or closures and the resulting rerouting signal. It does not explicitly name alternatives or state when not to use it, but the context is strong enough to guide selection.

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

All supply-chain-intelligence 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.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a specific and distinct supply chain intelligence need, such as monitoring port congestion, tracking commodity prices, or analyzing trade policy. While there are multiple tools related to signals and ports, each has a clearly defined purpose (e.g., real-time monitoring vs. trend analysis vs. predictive signals), reducing ambiguity.

Naming Consistency3/5

Most tools use the 'get_' prefix (e.g., get_port_congestion_trends, get_border_delays), but several tools lack it, such as commodity_price_monitor, port_congestion_monitor, and supply_chain_risk_assessment. This mix of 'get_' and non-'get_' naming creates inconsistency. Additionally, some names are noun-heavy (risk_pillar_breakdown) while others are verb-noun (commodity_price_monitor).

Tool Count3/5

At 31 tools, the server is on the higher end of acceptable scope for a comprehensive supply chain intelligence platform. However, some redundancy exists (e.g., multiple signal and port tools), and the count may overwhelm agents without clear prioritization. It is slightly above the ideal range for coherence.

Completeness5/5

The tool set covers the major aspects of external supply chain risk: commodities, transportation (ports, borders, air, rail, chokepoints), manufacturing, macroeconomic indicators, trade policy, natural disasters, and labor actions. It also includes analytical tools like trend analysis and predictive signals, leaving no obvious gaps for its stated purpose of monitoring global supply chain disruptions.

Resources