Skip to main content
Glama
Sign In

BerthTime

by com.berthtime
OverviewDiscussionsAdmin

Delayed shipments

list_delayed_shipments
Read-onlyIdempotent

Active shipments whose carrier ETA has slipped versus the first ETA BerthTime saw, by at least min_delay_hours, most delayed first. Use it for "what is late"; for shipments predicted to be late from the vessel position use list_shipments with eta_risk=likely_late. All arguments are optional: min_delay_hours (0-10000, default 24), limit (1-200, default 50). Returns: min_delay_hours, shipments[] {id, reference, ref_type, carrier, customer_reference, status, tracking_status, phase, pol, pod, eta, original_eta, delay_hours, predicted_eta, eta_risk, vessel, containers, booking_number, bl_number, tracked_via} (delay_hours = the slip). No paging.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum shipments returned, 1-200 (default 50).
companyNoWhich company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company.
min_delay_hoursNoMinimum ETA slip vs the first ETA seen, in hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavior beyond those annotations: it limits results to active shipments, defines delay as ETA slip versus the first ETA seen, says results are sorted most delayed first, explains the delay_hours field, and states there is no paging. It does not mention the company scoping parameter and says all arguments are optional while listing only two of the three, which is a minor 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?

The description is front-loaded: purpose, alternative, argument summary, and return shape. The return-field enumeration is long but useful because there is no output schema, and there is minor redundancy with the input schema for min_delay_hours and limit.

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?

For a three-parameter read-only list tool, the description covers selection criteria, the main alternative, sorting, no paging, and the returned fields. The main omission is company scoping, which is documented in the schema but not mentioned in the description.

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 description coverage is 100%, so all three parameters are already documented in the input schema. The description restates the min_delay_hours and limit ranges and defaults but adds no meaning beyond the schema, and it omits the company parameter entirely. With the schema carrying parameter documentation, a baseline 3 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 states a specific verb and resource: active shipments whose carrier ETA has slipped versus the first ETA seen, filtered by min_delay_hours and sorted most-delayed-first. It also distinguishes this from list_shipments with eta_risk=likely_late, so an agent can tell the two late-shipment views apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use this tool for "what is late" and names the alternative for predicted lateness from vessel position: list_shipments with eta_risk=likely_late. That is a clear when-to-use and when-to-use-something-else instruction.

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

All BerthTime toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources