MBD Travel

Tour departures

get_departures

Read-onlyIdempotent

Returns a tour's departures with the price of every occupancy slot for each (adult, single, extra bed, children, infant). Prices are not trimmed; every occupancy slot is listed. Past departures are excluded. Paged by date: default 12 per page; nextCursor is the cursor of the next page. The dates returned are the only departure dates the catalogue holds.

Input Schema

Name	Required	Description
`to`	No	Departures on or before this date (YYYY-MM-DD)
`from`	No	Departures on or after this date (YYYY-MM-DD)
`slug`	Yes
`limit`	No	Departures per page. Default 12.
`cursor`	No	nextCursor from the previous response.
`currency`	Yes	Price currency.
`language`	Yes	Catalogue language.

Output Schema

Name	Required	Description
`total`	Yes
`deepLink`	Yes
`departures`	Yes
`disclaimer`	No
`nextCursor`	Yes	Cursor of the next page; null on the last page.
`emptyReason`	Yes
`generatedAt`	No
`catalogueRefreshedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

addedOutput schema / properties / departures / items / properties / seatsLeft

Added value: +{
+  "description": "Seats left according to the supplier. Present only when 10 or fewer remain and the figure is under 36 hours old; absent otherwise. Not a hold.",
+  "minimum": 1,
+  "type": "integer"
+}

First observedOct 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description still adds real value: past departures are excluded, prices are untrimmed so every occupancy slot is present, and the returned dates are guaranteed to be the catalogue's complete set. Missing only operational details such as auth or rate limits.

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 what is returned, then constraints, then paging — a sensible order. One mild redundancy: 'with the price of every occupancy slot' and 'every occupancy slot is listed' restate the same guarantee.

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?

An output schema exists, so return shape needn't be explained, and the description covers the remaining gaps an agent would care about: exclusion of past departures, completeness of the date set, and the pagination contract. Only the date-range filter behavior is left entirely to the schema.

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 86%, so the schema already documents from/to, limit, cursor, currency and language. The description reinforces the default page size and the cursor-based paging contract but adds no syntax or constraint detail beyond what the schema already provides.

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 specific verb and resource ('Returns a tour's departures') and immediately scopes the payload to per-occupancy-slot pricing (adult, single, extra bed, children, infant). This clearly separates it from get_tour (catalogue detail) and search_tours (discovery) without needing any schema inspection.

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 implied by the content description and the 'past departures are excluded' constraint, but the description never says when to call this versus get_tour or search_tours, nor names any alternative. An agent can infer the intent but gets no explicit routing guidance.

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

All MBD Travel 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?