Skip to main content
Glama

Booking contact

booking_contact
Read-onlyIdempotent

How to reach the DharmikVibes retreats desk (WhatsApp number, email, enquiry page, partner email) and how booking works. This server cannot book or take payment.

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": "booking_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, non-open-world behavior, so the bar is lower. The description adds a genuinely new fact not in the annotations: the server cannot transact or take payment, which stops an agent from trying to complete a booking here — a meaningful behavioral boundary.

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?

Two short sentences, no filler, and the enumeration of channels is front-loaded before the negative constraint. Every clause carries information an agent would otherwise have to guess.

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 zero-param informational tool with no output schema, the description is close to sufficient: it enumerates what the agent will get back (four contact channels plus how booking works). It does not state the response format (e.g., static text vs. structured fields), which is the only remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, and the schema confirms an empty object with additionalProperties false. With zero parameters there is nothing for the description to disambiguate, so the baseline of 4 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?

The description names the concrete resource (the DharmikVibes retreats desk contact channels: WhatsApp, email, enquiry page, partner email) plus the booking-process explanation. It is not verb-shaped, but the content returned is unambiguous and no sibling (fetch, search, list_trips, get_trip_details, list_travel_articles) overlaps with contact lookup.

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 — an agent must infer this is the tool for "how do I contact them / how does booking work" questions. The one explicit constraint, "This server cannot book or take payment," usefully rules out a whole class of misuse, but no positive when-to-use condition or named alternative is given.

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