Skip to main content
Glama

Waiting times at anchor

port_waiting_times
Read-onlyIdempotent

Waiting times at anchor off a port: the median this week against what is normal there, and optionally the vessels waiting now. Credits: 5, nothing when we hold no figures for it. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

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": {
      "port": "<port>"
    },
    "name": "port_waiting_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYesA port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)
include_vesselsNoAlso list the vessels at anchor now (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, and the description goes further by disclosing the 5-credit cost, that no credits are charged when no figures exist, and the required paid plan tiers with a pricing link. That cost/auth information is exactly the kind of detail annotations cannot convey.

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?

Three short, front-loaded clauses: the metric comes first, the optional payload second, and cost/plan prerequisites last. No filler, and the most decision-relevant information leads.

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 output schema, the description does carry the burden of indicating what comes back (a weekly median versus normal, plus optionally vessels at anchor), which it does adequately. For a two-parameter read tool with full annotation coverage, this is nearly complete.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented, including the UN/LOCODE-or-name format and the default false for include_vessels. The description only reinforces that include_vessels adds the currently waiting vessels, adding little beyond the schema — the baseline 3.

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?

States a specific resource and metric: waiting time at anchor for a port, expressed as this week's median against the normal baseline, with an optional list of vessels currently waiting. That is concrete enough to differentiate from generic port tools, though it does not name an alternative sibling such as port_congestion.

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 only implied by the metric description; there is no explicit 'use this when you need X instead of Y' statement or exclusion. The plan and credit requirements give practical context, but not decision guidance between sibling port tools.

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