Skip to main content
Glama

Belline Connect

Book an open time

book_slot
Idempotent

Books a real appointment in the business's diary, with no owner answer in between. It works only for a business whose profile has instantBooking true and for a time that get_availability returned. Returns the booking reference and a link to change or cancel it.

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": {
      "slug": "<slug>",
      "agent_name": "<agent_name>",
      "service_id": "<service_id>",
      "date": "<date>",
      "start": "<start>",
      "customer_name": "<customer_name>"
    },
    "name": "book_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesThe day, YYYY-MM-DD, from get_availability.
slugYesBusiness slug.
notesNoAnything the business should know. Optional.
startYesThe start time, HH:MM, from get_availability.
agent_nameYesWhich assistant is booking, for example Claude.
request_idNoYour id for this booking, so a retry does not book twice.
service_idYesA service id from get_business_profile.
customer_nameYesThe person's name.
customer_emailNoAn email address. Phone or email is needed.
customer_phoneNoA phone number, with country code. Phone or email is needed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful context the annotations lack: the booking is real and confirmed without owner approval, and it returns a booking reference plus a change/cancel link. It stops short of describing failure modes or what happens to a slot if the call errors.

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 tight sentences, front-loaded with the action and its main constraint, then the eligibility rule, then the return value. Every sentence carries information an agent needs before calling.

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?

With no output schema, the description compensates by naming the return values (booking reference and change/cancel link). Preconditions and the sibling dependency are stated. Minor gaps remain around error behavior and what to do when instantBooking is false.

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 description coverage is 100%, so the baseline is 3; the description goes slightly beyond by tying date and start to values from get_availability and framing the call as a real write, which reinforces why request_id exists for retry safety. It doesn't explain the phone-or-email requirement itself, leaving that to the schema.

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 concrete verb and resource ("Books a real appointment in the business's diary") and immediately distinguishes itself from the inquiry-style siblings by adding "with no owner answer in between." An agent can tell this apart from create_inquiry or ask_business without opening either 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 explicit preconditions: the business profile must have instantBooking true, and the time must come from get_availability, which names a sibling as a prerequisite. It does not say what to do when those conditions fail (e.g. fall back to create_inquiry), so it stops short of full when-not/alternatives guidance.

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