Skip to main content
Glama

uPlanny — салоны и запись

Ссылка на запись

prepare_booking
Idempotent

Prepare a booking link for ONE service at ONE time (a «cart» of one item). Nothing is booked here and the time is not held: the person opens bookingUrl, checks the details, enters or corrects name, phone and e-mail, gives the consents themselves and books. The time must be one of those get_available_slots returns; it is checked now and again when the person confirms. If you already know the person's name, phone and e-mail, pass them: they pre-fill the form (they travel in the link's #fragment and are not stored by uPlanny). Cancelling and moving bookings are not available through this server.

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": {
      "serviceId": "<serviceId>",
      "start": "<start>"
    },
    "name": "prepare_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYesStart time from get_available_slots (`start`, e.g. 2026-11-18T10:00+03:00). Without an offset it is read in the salon's time zone.
masterIdNoA particular master (from the slot's masters). Leave out for any free master.
serviceIdYesService id.
customerNameNoOptional pre-fill: the person's name.
customerEmailNoOptional pre-fill: the person's e-mail.
customerPhoneNoOptional pre-fill: the person's phone, e.g. +7 999 123-45-67.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, idempotentHint=true, destructiveHint=false; the description adds the crucial nuance that nothing is booked and the slot is not held, and that availability is re-checked at confirmation. It also discloses that pre-filled PII travels in the link's #fragment and is not stored by uPlanny, which no annotation conveys. Minor gap: it does not state expiry/lifetime of the generated link.

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?

The non-booking nature is front-loaded where it matters most, and each sentence adds a distinct fact (no hold, slot source, pre-fill behavior, out-of-scope operations). It is slightly dense and could shed a clause or two, but nothing is redundant.

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 6-parameter tool with no output schema, the description covers what is returned (bookingUrl), who completes the booking, the validity constraint on start, and the scope limits. An agent has everything needed to call it correctly and explain the result to a user.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: customerName/customerEmail/customerPhone are optional pre-fills that are not persisted, and start must originate from get_available_slots. It also implies a single serviceId per call, reinforcing the one-item cart constraint.

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 and artifact ('Prepare a booking link') and bounds it tightly: 'ONE service at ONE time (a «cart» of one item)'. It immediately clarifies the tool does not book, which separates it from any true booking operation and frames its relationship to get_available_slots.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ('The time must be one of those get_available_slots returns') naming the sibling to call first, plus explicit exclusions ('Cancelling and moving bookings are not available through this server'). It also describes the correct downstream flow: hand bookingUrl to the person who completes the form themselves.

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