Shiptrail

Trends at sea

get_trends

Read-only

What the live fleet shows now, as Shiptrail's Trends page reads it: the ports where most ships wait at anchor and for how long, the ports most ships are heading for, traffic through the straits and canals, ships stopped in the Southern Bight off Rotterdam and Antwerp, and a group of ships whose broadcast positions show in one false spot. Made about every 30 minutes.

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

Input Schema

Name	Required	Description	Default
`limit`	No	At most this many ports, and straits and canals, in each list.

Output Schema

Name	Required	Description
`at`	Yes	When these trends were made.
`url`	Yes	The Trends page.
`queues`	Yes	Ports with the most ships waiting at anchor, most first.
`heading`	Yes	Ports the most ships are heading for, most first.
`straits`	Yes	Ships in each watched strait and canal now.
`southernBight`	No	Large ships stopped at the southern end of the North Sea; absent when fewer than 20 are.
`falsePositions`	No	Ships drawn within 3 km of one point at impossible speeds or after impossible jumps, a sign their positions are false; absent when no such group shows.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavioral context by disclosing the refresh cadence ('Made about every 30 minutes'), which tells the agent how stale the snapshot may be. It also signals the scope is a fixed set of aggregate sections rather than an arbitrary query, so the agent knows to expect a multi-section result. No contradiction with annotations.

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?

It is one long sentence, but the leading clause establishes freshness and source before the enumerated contents, so it is well front-loaded. The list of five data categories is dense yet each item earns its place by telling the agent what sections come back; only minor tightening is possible.

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

Completeness5/5

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

An output schema exists, so return-value shape need not be explained, and the description still covers scope, data freshness, and the categories included. For a read-only aggregate tool with one optional parameter, nothing an agent needs in order to call it correctly is missing.

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% and the single 'limit' parameter is fully documented in the schema as capping each list at 1–20 with default 5. The description adds nothing about the parameter, which is acceptable given the schema already carries the meaning, so the baseline of 3 applies.

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 gives a specific verb-and-resource framing ('What the live fleet shows now, as Shiptrail's Trends page reads it') and then enumerates the exact aggregates returned: anchor-wait ports, destination ports, strait/canal traffic, ships stopped in the Southern Bight, and mislocated broadcasts. That enumeration makes it unmistakable against siblings like get_port, get_ship, get_ships_near, and the search_* tools.

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 phrase 'what the live fleet shows now' — the agent can infer this is the live aggregate snapshot versus the entity-level lookups, but no alternative is named and no when-not-to-use condition is stated. The 30-minute cadence hint helps but is framed as a fact, not routing guidance.

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

All Shiptrail tools Inspect

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

Need Help?