Skip to main content
Glama

Full of Joy · Croatia private tours

Book a tour

request_booking

Book a Full of Joy tour online for one tour, date and group. The team confirms the booking to the traveller by email with the final price and payment terms. Nothing is charged online. Only call this after the traveller agreed to share their name and email.

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": {
      "tour": "<tour>",
      "date": "<date>",
      "persons": "<persons>",
      "name": "<name>",
      "email": "<email>"
    },
    "name": "request_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesTour date, YYYY-MM-DD.
nameYesTraveller full name.
noteNoOptional message: pick-up place, interests, children, etc.
tourYesTour key from list_tours.
emailYesTraveller email address for the reply.
phoneNoOptional phone number.
optionNoOption key from get_tour. Default: the first option.
countryNoOptional country of residence.
personsYesNumber of travellers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the booking is a request, not a confirmation; the team replies by email with final price and payment terms; and nothing is charged online. That clarifies the openWorldHint/non-idempotent profile in practical terms an agent needs before committing a traveller.

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?

Three sentences, front-loaded with the action and scope, then the outcome, then the precondition. No filler or repeated field lists.

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 9-parameter mutation with no output schema, the description covers what happens after calling and the no-charge guarantee. It leaves minor gaps, such as what the response contains or what occurs when the requested date is unavailable, but nothing critical to invoking it correctly is missing.

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 description coverage is 100%, so all nine parameters (including option, note, phone, country) are already documented. The description only reinforces 'one tour, date and group' and adds no syntax, defaults or constraint detail beyond the schema, so baseline 3 applies.

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?

States a specific verb ('Book') and resource ('Full of Joy tour'), and scopes it to 'one tour, date and group', which separates it from list_tours, get_tour and check_availability without opening any schema.

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?

Gives a hard precondition: 'Only call this after the traveller agreed to share their name and email.' That is a clear when-to-use gate, but the description never tells the agent to verify availability first or which sibling to use if the date is unavailable.

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