Skip to main content
Glama

List retreats, yatras and experiences

list_trips
Read-onlyIdempotent

Every yatra, residential retreat, experience and group session with place, duration, the published price label and its kind (from_price, indicative, on_enquiry) and the page URL. Optional type filter: "journey", "retreat", "experience", "session".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_trips"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional: journey, retreat, experience or session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value by disclosing exactly what each item contains, including the price-label taxonomy (from_price, indicative, on_enquiry) and the page URL. It omits ordering and pagination behavior for what is a full-catalog listing.

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?

Two dense sentences with no filler, and the catalog contents are front-loaded ahead of the filter detail. The opening is a verbless fragment, which costs a little immediate clarity.

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 usefully compensates by enumerating the returned fields, and one optional filtered parameter is fully covered. What remains thin is list-level behavior such as result ordering or whether the full catalog can be large.

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 100% and the single parameter already carries a description listing the accepted values, so the schema does the heavy lifting. The description restates the same four values as a filter and frames them as the 'type', adding little beyond what the schema provides.

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 the resource (yatras, residential retreats, experiences, group sessions) and enumerates the return fields, so an agent knows this is a catalog-listing tool rather than a detail lookup. It never states a verb explicitly and does not name get_trip_details as the single-item alternative, so it falls short of full sibling differentiation.

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: 'Every ...' signals that this returns the complete catalog with an optional narrowing filter, which steers an agent away from expecting search-style behavior. There is no explicit guidance on when to prefer this over get_trip_details or search, and no 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