get_hormuz_transitsShips through the Strait of Hormuz per day, split tanker and cargo, measured by Helious from live ship tracking.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | How many days back. | |
| fresh | No | Set true to ask for the live view of this one call, for 5 credits, where the connected account otherwise receives it an hour behind. Accepted and free where the account is already live. No effect without a key. |
Changes observed during successful MCP inspections.
Input schema / properties / fresh / descriptionPrevious value: -"Not on Pro or Ultimate? Set this to true and this one call answers live for 5 credits. Left out, Free, Squawk and Starter get the answer an hour behind for 1 credit. Pro and Ultimate are live already, so it costs nothing extra there. No effect without a key."New value: +"Set true to ask for the live view of this one call, for 5 credits, where the connected account otherwise receives it an hour behind. Accepted and free where the account is already live. No effect without a key."Input schema / properties / freshAdded value: +{
+ "description": "Not on Pro or Ultimate? Set this to true and this one call answers live for 5 credits. Left out, Free, Squawk and Starter get the answer an hour behind for 1 credit. Pro and Ultimate are live already, so it costs nothing extra there. No effect without a key.",
+ "type": "boolean"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description usefully adds provenance (Helious, live ship tracking) and the tanker/cargo split. It omits material behavioral facts an agent would care about, notably that the default view can lag roughly an hour behind and that a paid live view exists — though that detail lives in the `fresh` parameter description rather than here.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with zero filler: subject (ships), scope (per day), dimension (tanker/cargo), and source (Helious). Nothing to trim.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, so the description bears responsibility for describing the return shape; it gives dimensionality (per day, split by vessel type) but not format, units, or default lookback when `days` is absent. Combined with the undisclosed default latency, an agent has gaps before calling.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both `days` and `fresh` are already documented in structured data; baseline 3 applies. The description adds nothing about parameter semantics — no default range, no units — beyond clarifying what 'ships' means for interpretation of results.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource: daily ship transits through the Strait of Hormuz, broken down by tanker vs. cargo, with a named data source. An agent can tell exactly what data comes back. It doesn't name a sibling, but no sibling overlaps this domain, so differentiation is inherent rather than stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description never says when to use this tool, what the default time window is when `days` is omitted, or how it relates to any alternative. Usage must be inferred entirely from the name and schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.