Ferryhopper

Trip Details

trip_details

Read-only

Get full details for a single sailing leg, looked up by the tripId returned by search_trips_v2. Returns the trip's departure/arrival time, ports, and operating company, plus the vessel's technical specs, onboard amenities, and photos. Use this to answer questions about a vessel such as: does it have wifi / a restaurant / a snack bar / an open deck / a lift or elevator / wheelchair or disabled access / a designated smoking area? Is it pet-friendly, or does it allow pets on board? Does it have cabins, or a garage / vehicle deck for cars and motorbikes? How many passengers or vehicles does it carry (capacity)? How long is the vessel (length in meters)? What is its IMO number or MMSI (maritime identification numbers used for registry/tracking lookups)? Is this vessel accessible, family-friendly, or suitable for passengers who need mobility assistance? What does the vessel look like (photos)? If no detailed specs exist for the vessel in the source system, vessel.hasDetails is returned as false and every spec/amenity field is null — this means the data is unavailable, not that the vessel lacks that amenity. Also returns the trip's bookable accommodation tiers (seat/cabin classes) with their price and a photo of that accommodation, when available. Throws if the tripId is malformed or the trip is no longer bookable (e.g. it has already departed, was cancelled, or sold out) — re-run search_trips_v2 to get a fresh tripId in that case.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tripId`	Yes	The trip identifier for a single sailing leg, as returned in tripsById/bookingSolutions by search_trips_v2. Do not fabricate this value.

Output Schema

TableJSON Schema

Name	Required	Description
`trip`	Yes
`vessel`	Yes
`vesselImages`	Yes	Vessel photos ordered for display (e.g. in a carousel). Empty if no photos are available.
`accommodations`	Yes	Bookable accommodation tiers for this trip (seat/cabin classes), one entry per fare code as priced by the source system — multiple entries may share the same type/image at different prices (e.g. different berth counts within the same cabin category).

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, but the description goes far beyond that. It explains the critical semantic that null spec/amenity fields mean 'data unavailable, not that the vessel lacks that amenity,' which is essential for correct interpretation. It also discloses the throw behavior on malformed or unbookable trips and instructs recovery. This is substantial behavioral context not present in 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?

The description is long but extremely well-organized: a one-sentence summary, a list of concrete queries it supports, null-semantics explanation, accommodation tier note, and error handling. Each section serves a distinct purpose and there is no redundancy. While it could be trimmed, the length is justified by the breadth of questions the tool answers, so it earns a 4 rather than a 3.

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?

With an output schema present, return structure is already documented. The description covers the input requirement (tripId from search_trips_v2), the data semantics (nulls mean unavailable), the error conditions and recovery, and the scope of information returned (including accommodation tiers). Nothing an agent needs to correctly invoke and interpret this tool is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines tripId as the identifier from search_trips_v2 and warns not to fabricate it. The description adds meaning by reinforcing the source requirement and explaining that an invalid or non-bookable trip causes an error, implying the value must be current and valid. This is a meaningful addition beyond the schema's static definition, though not excessive.

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 opens with a precise verb and resource: 'Get full details for a single sailing leg,' and explicitly states the lookup mechanism via tripId from search_trips_v2. This clearly separates it from siblings like search_trips_v2 (which searches) and get_ports (which fetches ports). The purpose is unambiguous and immediately actionable.

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?

The description explicitly ties usage to search_trips_v2: 'looked up by the tripId returned by search_trips_v2.' It provides a concrete list of question types it answers, and gives explicit error-handling instructions: if it throws because the trip is no longer bookable, 're-run search_trips_v2 to get a fresh tripId.' This is textbook guidance on when and how to use the tool versus alternatives.

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

All Ferryhopper tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Each tool serves a distinct purpose (ports, connections, disruptions, trip search, trip details), but the presence of both search_trips and its deprecated v2 creates overlap. The clear deprecation note mitigates ambiguity, so it's mostly distinct.

Naming Consistency4/5

Most tools follow a verb_noun pattern (get_direct_connections_for_ports, get_disruptions, get_ports, search_trips, search_trips_v2). However, trip_details swaps the order to noun_noun, which deviates from the established convention.

Tool Count5/5

Six tools well cover the domain of ferry travel information: port lookup, route discovery, trip search (with v2 supporting round-trips), trip details, and disruptions. No redundancy or bloat; each tool earns its place.

Completeness4/5

The surface covers the key informational workflows: finding ports, routes, trips, and details, plus disruption alerts. It lacks booking functionality, but the server's purpose appears to be planning/quoting rather than booking, so the gap is acceptable.

Resources

Need Help?