Skip to main content
Glama

Open a trip request with Maya

start_trip_request

Sends the traveler's trip request to Maya as a new lead, exactly like her website questionnaire. Use it only when the traveler asked to be contacted by MDJ and agreed to share these details. Maya or her team reply by email. Set dry_run to true to validate without sending.

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": {
      "first_name": "<first_name>",
      "email": "<email>",
      "destination": "<destination>",
      "traveler_consent": "<traveler_consent>"
    },
    "name": "start_trip_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe traveler's email address.
phoneNoOptional, with country code.
adultsNo
countryNoCountry the traveler lives in.
dry_runNo
serviceNofull_custom: Maya plans and books the entire trip. execute_existing: the traveler already has an itinerary and wants it booked and supported.
childrenNo
last_nameNo
agent_nameNoName of the AI assistant sending this request.
first_nameYes
descriptionNoWhat the traveler wants, in their words.
destinationYes
hotel_levelNo
return_dateNo
trip_lengthNoFor example "14 days".
children_agesNo
departure_dateNoYYYY-MM-DD or a month.
traveler_consentYesMust be true: the traveler asked to be contacted by MDJ.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / service / description
      Previous value: -"full_custom: Maya plans and books the whole trip. execute_existing: the traveler already has an itinerary and wants it booked and supported."New value: +"full_custom: Maya plans and books the entire trip. execute_existing: the traveler already has an itinerary and wants it booked and supported."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag openWorldHint=true and non-idempotent, and the description adds the context that matters most: the lead goes to a third party, the reply comes back by email rather than as a tool result, and dry_run validates without sending. The email-reply channel is especially valuable since there is no output schema to explain what comes back.

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?

Four tight sentences, front-loaded with the action and followed by the consent gate, delivery channel, and dry-run escape hatch. The website-questionnaire comparison earns its place as a compact mental model; nothing is padded.

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?

For a high-parameter outbound mutation with no output schema, the definition covers purpose, consent precondition, response channel, and a safe test mode. It stops short of stating what happens on validation failure or whether repeat submissions create duplicate leads, which would close the remaining gap.

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?

With 18 parameters and only 50% schema description coverage, the description compensates for the two riskiest gaps: it explains dry_run's validate-only behavior (undocumented in the schema) and reinforces traveler_consent as a hard gate. It says nothing about hotel_level, trip_length, children_ages, agent_name, or date formats, so roughly half the surface still relies on the schema alone.

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 gives a specific verb and resource: it 'sends the traveler's trip request to Maya as a new lead,' and the website-questionnaire analogy pins down the artifact being created. It does not explicitly contrast with siblings like estimate_trip, but the submission/lead-creation purpose is unmistakable.

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?

It states an explicit gating condition: 'Use it only when the traveler asked to be contacted by MDJ and agreed to share these details.' That is a clear when-to-use plus a when-not-to-use exclusion, which is exactly what an agent needs before firing an outbound lead.

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