Skip to main content
Glama

BRAINIAC Maritime & Shipping Intelligence

Analyze port congestion

maritime-intelligence_port-congestion-analyze

Analyze caller-supplied port wait, queue, and berth-occupancy samples. Live terminal systems are not queried. Price $0.04 USDC. POST /api/v1/maritime-intelligence/port-congestion-analyze. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "maritime-intelligence_port-congestion-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
vesselsNo
aisPointsNo
fetchOfacNo
waypointsNo
cargoEventsNo
portSamplesNo
assumedSpeedKnNo
demurrageCasesNo
destinationLatNo
destinationLonNo
ownershipRecordsNo
sanctionsEntriesNo
gapThresholdHoursNo
deviationThresholdKmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose behavior an agent could not infer from the schema: the endpoint, the $0.04 USDC price, and that unpaid calls return 402 and do not execute. That payment-gating and data-sourcing disclosure is genuinely valuable. It stops short of describing the analysis itself (what output, determinism, minimum data sufficiency), which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, each carrying a distinct fact (what it analyzes, data sourcing, price, endpoint, payment failure), with the core purpose front-loaded. No filler or repetition, though the bare POST path line is only marginally useful to an agent.

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

Completeness1/5

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

Against a 20-parameter tool with no annotations, no output schema, and zero schema description coverage, the definition is far too thin. Nothing explains which of the many optional inputs are needed for a meaningful congestion result, how the text/csv/json/file channels relate, or what the caller gets back — an agent cannot call this correctly from the description alone.

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

Parameters2/5

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

There are 20 parameters at 0% schema description coverage, so the description must compensate and largely does not. 'Port wait, queue, and berth-occupancy samples' hints at the portSamples shape but says nothing about the alternate input channels (csv, json, text, file, files), asOf, the threshold parameters, or the many analysis-only arrays like vessels, aisPoints, waypoints, cargoEvents, and demurrageCases.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (Analyze) and a specific resource (caller-supplied port wait, queue, and berth-occupancy samples), so an agent knows immediately this is a port-congestion computation rather than an AIS, route, or sanctions tool. It does not explicitly name a sibling to distinguish itself from, but the domain nouns are distinctive enough against the adjacent siblings.

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?

'Caller-supplied ... Live terminal systems are not queried' is a real usage constraint: the agent learns it must supply the sample data itself and cannot expect the tool to fetch it. However, there is no explicit when-to-use/when-not guidance and no routing to an alternative (e.g. the ETA or route-deviation siblings) for cases this tool does not cover.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources