Skip to main content
Glama
Sign In

Ignix

by social.ignix
OverviewDiscussionsAdmin

Book an appointment

create_appointment
Destructive

Book an appointment on behalf of the business (for example one that came in by phone). For a restaurant table or an activity, pass partySize (how many people). Paid services are NOT charged when booked from here: the business takes the payment itself (only the public booking page charges online). Checks the slot is still free, assigns a person or room, creates the Google Calendar event, stores the customer details on their contact card (phone and custom answers as custom fields, plus the "booking" tag; the contact is created if it does not exist) and, if an email was given, sends the customer a confirmation with the appointment attached (.ics), branded as the business. Confirm the details with the user before calling it.

Input Schema

NameRequiredDescriptionDefault
nameNoCustomer name.
withNoPerson or room (name or id). Omit to assign whoever is free (for restaurants, the smallest table that fits).
emailNoCustomer email (reminders go there).
phoneNoCustomer phone.
startYesStart, "YYYY-MM-DD HH:MM" in the business time zone (from get_booking_availability).
answersNoAnswers to the business's own questions, keyed by the intake field key (see get_booking_settings).
serviceYesService name or id.
partySizeNoHow many people (diners, participants), within the service partyMin-partyMax. Defaults to the minimum (1 for normal appointments).
workspaceIdNoDefaults to the workspace this connection is scoped to.
idempotencyKeyNoOptional. A unique id for this action (16-128 chars: letters, digits, _ : . -). If you are unsure whether a call went through (timeout, network error), repeat it with the SAME idempotencyKey and the same arguments: you get the original result and nothing is done twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / partySize
      Added value: +{
+  "description": "How many people (diners, participants), within the service partyMin-partyMax. Defaults to the minimum (1 for normal appointments).",
+  "type": "number"
+}
    • changedInput schema / properties / with / description
      Previous value: -"Person or room (name or id). Omit to assign whoever is free."New value: +"Person or room (name or id). Omit to assign whoever is free (for restaurants, the smallest table that fits)."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by enumerating every side effect: slot availability check, person/room assignment, Google Calendar event creation, contact creation or update with custom fields and a 'booking' tag, and an outbound branded confirmation email with .ics attached. That outbound-email consequence is exactly the kind of externally visible effect an agent must know before invoking a non-read-only tool.

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?

Front-loaded with the purpose and the partySize rule before the long side-effect sentence, so an agent can stop reading early. The side-effect sentence is a dense run-on that could be split, but every clause carries operational information rather than filler.

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 10-parameter, no-output-schema mutation tool with nested 'answers', the description is nearly complete: it covers prerequisites, side effects, contact card persistence and notification behavior. It stops short of saying what is returned or what happens when the slot is no longer free, which an agent handling failures would want.

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; the description still adds conditional meaning by telling the agent to pass partySize for restaurant tables or activities and how diners/participants are counted, and by tying answers to the business's intake field keys. The remaining parameters (with, workspaceId, idempotencyKey) are left entirely 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 specific verb and resource ('Book an appointment') and immediately scopes it as 'on behalf of the business (for example one that came in by phone)', which separates it from the public booking page and from sibling tools like list_appointments and cancel_appointment. The purpose is unmistakable without opening the schema.

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?

Explicitly names the trigger case (appointments taken by phone) and names an exclusion: paid services are not charged here because the business takes payment itself, only the public page charges online. It also adds a procedural precondition, 'Confirm the details with the user before calling it,' and points at get_booking_availability / get_booking_settings as prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ignix toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources