Skip to main content
Glama

Maritime chokepoints: ships per day (IMF PortWatch, weekly)

get_chokepoints
Read-only

Free. Ships and tankers per day through maritime chokepoints (Strait of Hormuz, Bab el-Mandeb, Suez, Cape of Good Hope, Malacca, Panama, Bosporus and others): average of the last 7 days of data vs the same 7 days a year earlier, plus the last daily counts. IMF PortWatch AIS-based estimates via HDX, updated weekly with a few days' lag.

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": "get_chokepoints"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint) and scope (openWorldHint), so the description's job is to add operational context — and it does: free access, AIS-based estimates, weekly refresh cadence, and a multi-day publication lag. It does not specify response structure (units, per-chokepoint grouping) beyond the comparison metrics, which is the main remaining gap.

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?

A single dense sentence with the cost signal front-loaded and the comparison semantics ('last 7 days vs the same 7 days a year earlier') placed before the provenance footnote. Slightly parenthetical-heavy, but every clause carries information.

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?

With no parameters and no output schema, the description must convey what comes back, and it does name the return contents (7-day average, year-over-year comparison, last daily counts) plus freshness. Exact field names and units remain unspecified, a minor gap for a read-only snapshot 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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline applies. The description usefully clarifies that the result set spans all listed chokepoints ('and others') rather than requiring a selection.

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 names a specific resource and metric ('Ships and tankers per day through maritime chokepoints'), enumerates concrete chokepoints, and identifies the underlying source (IMF PortWatch AIS via HDX). An agent immediately knows this returns maritime transit volumes rather than any of the unrelated sibling datasets.

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?

Usage is implied rather than stated: 'Free' signals no cost barrier, and 'updated weekly with a few days' lag' tells the agent not to treat the figures as real-time. There is no explicit 'use this when...' framing and no named alternative, though with zero parameters there is little ambiguity about how to invoke it.

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.