Skip to main content
Glama

MolTravel

by com.moltravel
OverviewDiscussionsAdmin

tourradar_b2b-tour-departures

[tourradar] Use this when the user asks about available departure dates, pricing for specific dates, or needs to validate if a departure date is available.

Returns a list of departures for a specific tour within a date range, including availability status, pricing, and booking information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number. Default is 1
tourIdYesTour ID
currencyNoCurrency to return prices in. Use this only when the user explicitly asks for a specific currency. Otherwise the user's default (based on location) is used.
dateRangeYesReturns only departure dates in the desired range

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / currency
      Added value: +{
+  "description": "Currency to return prices in. Use this only when the user explicitly asks for a specific currency. Otherwise the user's default (based on location) is used.",
+  "enum": [
+    "USD",
+    "EUR",
+    "GBP",
+    "AUD",
+    "NZD",
+    "CAD"
+  ],
+  "type": "string"
+}
  2. Changed6 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / dateRange / additionalProperties
      Removed value: -false
    • addedInput schema / properties / dateRange / properties / end / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • addedInput schema / properties / dateRange / properties / start / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / tourId / maximum
      Added value: +9007199254740991
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the return content (availability, pricing, booking info) but does not mention whether the operation is read-only, any permissions required, pagination behavior, or potential limitations. It is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise: two sentences with the usage context front-loaded. Every sentence adds value without redundancy.

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?

With no output schema, the description partially explains the return values (list of departures with availability, pricing, booking info). It covers the primary use case but omits pagination details and any edge-case behaviors, leaving minor gaps.

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?

All parameters have descriptions in the schema (100% coverage), so the baseline is 3. The tool description reinforces the use of tourId and dateRange but does not add new syntactic or format details beyond the schema. The page parameter is not mentioned in the description.

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 clearly identifies the tool as returning a list of departures for a tour, with specific capabilities (availability status, pricing, booking info). It mentions a date range and distinguishes this from other tourradar tools like tour details, FAQs, or booking.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool: when a user asks about departure dates, pricing for specific dates, or validating availability. However, it does not explicitly name alternatives or provide 'when not to use' guidance, so it falls short of a perfect score.

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

All MolTravel 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