Skip to main content
Glama

QConsul LLC

Prepare booking

prepare_booking

Hold a Standard Hourly slot ($425.00), or the first session of an Executive 1:1 Subscription and its recurring monthly day and time, for 30 minutes and return a secure payment link; the booking is confirmed only when payment succeeds.

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": {
      "slot": "<slot>",
      "name": "<name>",
      "title": "<title>",
      "company": "<company>",
      "email": "<email>",
      "phone": "<phone>",
      "need": "<need>"
    },
    "name": "prepare_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCustomer full name.
needYesWhat the customer wants to cover in the session.
slotYesSlot start from check_availability, ISO 8601.
emailYesCustomer email.
phoneYesCustomer phone number.
titleYesCustomer job title.
companyYesCustomer company or organization.
patternNoExecutive 1:1 only: standing monthly pattern (ordinal 1-4 or -1 for last; weekday 1-4 Mon-Thu; hour 10-16 PT). Defaults to the first session's pattern.
serviceNoService id from list_services; defaults to standard-hourly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, non-idempotent, open-world mutation. The description adds genuinely useful behavior: a 30-minute temporary hold, the $425.00 price point, that a payment link is returned, and that confirmation is contingent on payment success. It stops short of explaining hold expiry consequences or link validity.

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?

It is a single dense sentence that front-loads the core action and price before the payment-link detail. Nothing is wasted, though the one-sentence form makes the hold-duration and confirmation condition easy to skim past.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter mutation with a nested pattern object and no output schema, the description supplies what the schema cannot: the temporary-hold model, the payment-link return, and the payment-gated confirmation rule. Combined with full schema coverage and mutation annotations, an agent has enough to call this correctly.

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%, so parameter documentation is already complete, and the description adds only the linkage between the executive service and its recurring monthly pattern. It does not add format, constraint, or dependency detail beyond what the schema already states for slot, service, or pattern.

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 action (hold a slot), the two service variants it covers, the price, the hold duration, and the return value (a secure payment link). It also distinguishes this from a completed booking by stating confirmation only occurs on payment success, which separates it from confirm_booking.

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 implied rather than stated: the reader infers this is the step between selecting a slot and paying, and that confirm_booking finishes the job. There is no explicit when-to-use/when-not statement, no mention of calling check_availability or list_services first (that only appears in the schema), and no guidance on what to do if the hold expires.

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