Skip to main content
Glama
Sign In

BerthTime

by com.berthtime
OverviewDiscussionsAdmin

Arriving soon

list_arriving_shipments
Read-onlyIdempotent

Active shipments not yet arrived whose carrier ETA falls within the next N days, soonest first. Use it for "what arrives this week"; for an exact date range or other filters use list_shipments with eta_after / eta_before. All arguments are optional: days (1-120, default 7), limit (1-200, default 50). Returns: days, 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}. No paging: raise limit or narrow days.

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_arriving_shipments"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-ahead window in days from now.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds the traits that matter: only not-yet-arrived active shipments, soonest-first ordering, no paging, and the workaround (raise limit or narrow days). Because no output schema exists, listing the returned fields (shipments[] with id, eta, delay_hours, predicted_eta, eta_risk, etc.) supplies return-shape information the agent would otherwise lack.

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?

Front-loaded with the core definition, then usage routing, then arguments, then return shape — a sensible order with no filler sentences. It slightly duplicates schema-stated defaults and bounds (days 1-120 default 7, limit 1-200 default 50), which is minor waste.

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 filtered read tool with no output schema, it covers window semantics, ordering, result shape, and the no-pagination constraint, which is nearly everything needed to call it correctly. The only gap is that company scoping — present in the schema and relevant for a multi-company connection — is not mentioned; it need not restate return values or safety, which annotations already handle.

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 days and limit ranges are already documented in the schema; the description only restates the defaults and bounds. It never mentions the company argument, so it adds essentially no meaning beyond the schema.

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?

States a precise verb+resource+scope: 'Active shipments not yet arrived whose carrier ETA falls within the next N days, soonest first'. It also explicitly distinguishes itself from the sibling list_shipments, so an agent can pick between them 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?

Gives a concrete usage cue ('what arrives this week') and names the alternative with the exact parameters that replace it (list_shipments with eta_after / eta_before) for exact date ranges or other filters. When-to-use and when-not-to-use are both explicit.

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