Skip to main content
Glama

Search retreats and experiences

search
Read-onlyIdempotent

Search DharmikVibes retreats, yatras, experiences, group sessions, travel-help pages and articles. Returns ids, titles, URLs and a snippet; pass an id to fetch for the full text.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for, e.g. "Kashi yatra with Ganga aarti" or "retreat near Rishikesh".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"What to look for, e.g. \"Ayurveda detox Kerala\" or \"retreat near Rishikesh\"."New value: +"What to look for, e.g. \"Kashi yatra with Ganga aarti\" or \"retreat near Rishikesh\"."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent, closed-world operation. The description adds useful behavioral context by revealing the return fields (ids, titles, URLs, snippet) and explaining that full text requires a follow-up `fetch` call.

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 two well-structured sentences with no wasted wording. It is front-loaded with what is searched and follows with return behavior and the next step.

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 search tool with no output schema, the description sufficiently covers what is searched, the key return fields, and the follow-up `fetch` behavior. It could optionally mention result limits or pagination, but those gaps are minor given the tool's simplicity and existing annotations.

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 only one parameter, and the schema already fully documents `query` with examples. The description does not add additional syntax, formatting, or search-operator guidance beyond what the schema provides.

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 names a specific verb and resource set: search DharmikVibes retreats, yatras, experiences, group sessions, travel-help pages, and articles. It also clarifies the relationship to the `fetch` sibling by saying to pass an id for full text, making the boundary clear.

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?

It gives a clear usage pattern: search to discover items, then pass an id to `fetch` for full text. It does not explicitly state when not to use this tool or when to use listing siblings like `list_trips`, but the core when-to-use guidance is present.

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