Skip to main content
Glama

Price range for a fully planned trip

estimate_trip
Read-only

A price range for a fully planned and booked MDJ trip, from the ranges MDJ publishes (per person per day, by hotel level, for a couple, everything included except international flights). The final price always comes from a supplier quote for the specific trip. The same calculation for people: https://planning.mydailyjourneys.com/tools/trip-cost-calculator

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "days": "<days>",
      "travelers": "<travelers>"
    },
    "name": "estimate_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
travelersYes
destinationNoCountry: Vietnam, Thailand or Cambodia.
hotel_levelNoOptional. Without it, all 3 levels are returned.
start_monthNoOptional: the month the trip starts, a month name or a number from 1 to 12. With a destination, each range is adjusted to that month where at least 5 real MDJ trips at that hotel level back it; otherwise the published year-round range applies, with a peak-season note.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / start_month / description
      Previous value: -"Optional: the month the trip starts, a month name or a number from 1 to 12. It adds a season note."New value: +"Optional: the month the trip starts, a month name or a number from 1 to 12. With a destination, each range is adjusted to that month where at least 5 real MDJ trips at that hotel level back it; otherwise the published year-round range applies, with a peak-season note."
  2. Changed1 schema field changed
    • changedInput schema / properties / start_month / description
      Previous value: -"Optional: the month the trip starts, a month name or a number from 1 to 12. For Vietnam it adds figures from the MDJ price index of real quotes for trips starting in that season."New value: +"Optional: the month the trip starts, a month name or a number from 1 to 12. It adds a season note."
  3. Changed1 schema field changed
    • addedInput schema / properties / start_month
      Added value: +{
      +  "description": "Optional: the month the trip starts, a month name or a number from 1 to 12. For Vietnam it adds figures from the MDJ price index of real quotes for trips starting in that season.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint true, openWorldHint false), and the description adds genuinely useful behavior: the pricing basis (per person per day, by hotel level, couple, all-inclusive except flights), that the result is a range rather than a binding price, and the month-adjustment rule with its 'at least 5 real trips' fallback and peak-season note. It does not state currency or the shape of the returned range.

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?

Three front-loaded sentences with no filler; the inclusion/exclusion caveat and the estimate-not-quote warning arrive before the supporting link. The trailing calculator sentence is slightly awkwardly phrased but earns its place by giving an equivalent human-facing reference.

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

Completeness3/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 must carry the return contract, and it only partly does: it says a range is returned and that all three hotel levels appear when hotel_level is omitted, but currency, whether ranges are per-person or per-trip totals for the given travelers, and behavior when destination is omitted are unstated.

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 60%: destination, hotel_level and start_month are well documented, while days and travelers are only bounded by min/max with no prose. The description partially compensates by explaining the pricing basis and the 'without hotel_level, all 3 levels are returned' default, but it never explains how the travelers count interacts with ranges quoted 'for a couple', which is the most likely source of misuse.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete artifact — a price range for a fully planned and booked MDJ trip — built from published per-person-per-day, hotel-level ranges for a couple with everything except international flights. That is specific enough to distinguish an estimate from a booking or quote tool, but it never names or contrasts the closest sibling (get_price_index), leaving the boundary to inference.

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?

'The final price always comes from a supplier quote' implies this is a pre-quote estimate, which is real usage context, and the calculator URL points to an equivalent for humans. There is no explicit statement of when to choose this over get_price_index or start_trip_request, and no prerequisites or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources