Skip to main content
Glama

Trip details

get_trip_details
Read-onlyIdempotent

One retreat, yatra or experience in full: place, duration, price label, the day-by-day itinerary, inclusions and exclusions, and how to book or ask.

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": {
      "id": "<id>"
    },
    "name": "get_trip_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id from search or list_trips (e.g. "journeys/kashi-shiva-consciousness", "retreats/return-to-yourself", "experiences/antar-yatra", "blog/<slug>") or a wellness.dharmikvibes.com URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds real value by disclosing the payload contents (itinerary, inclusions/exclusions, booking channel), which matters because there is no output schema. It stops short of noting what happens on an unknown id or that a site URL is also accepted.

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?

A single dense sentence, front-loaded with the resource ('One retreat, yatra or experience in full') followed by a compact enumeration of returned fields. No filler, no repetition of the title.

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 one-parameter read tool with full annotations, the description covers the main open question, namely what comes back, since no output schema exists. The gap is that 'how to book or ask' could be misread as performing a booking, when booking_contact is the sibling for that action.

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?

There is exactly one parameter with 100% schema description coverage, and the schema already documents accepted id shapes and examples. The description adds no further meaning about the id, so the baseline of 3 applies.

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?

States a specific verb-resource pair implicitly ('One retreat, yatra or experience in full') and enumerates exactly what the response covers: place, duration, price label, itinerary, inclusions/exclusions, booking path. An agent can tell this is a single-item detail fetch, distinct from list/search, though the description never names those siblings to reinforce the split.

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 only implied: the tool returns one item 'in full', and the schema tells the agent the id comes from search or list_trips. The description itself never says when to call this versus list_trips or search, nor what to do when the id is unknown. Adequate but reliant on inference.

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