Skip to main content
Glama
chrischall

easytable-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

easytable_create_booking

Destructive

Create a restaurant reservation from an open booking-widget tab. It submits guest details and the Turnstile token only after user confirmation.

Instructions

Create a restaurant booking. Reads the Cloudflare Turnstile token from your signed-in booking-widget tab (via the bridge) and submits it with the reservation — so a book.easytable.com/book/?id= tab must be open and loaded. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The first call makes NO network call.

Input Schema

NameRequiredDescriptionDefault
idYesRestaurant id — the `id` in a book.easytable.com/book/?id=<id> link.
dateYesBooking date, ISO YYYY-MM-DD (from easytable_list_dates).
langNoWidget language code (en, se, da, …). Defaults to en.en
nameYesGuest name on the booking.
timeYesTime slot HH:MM, 24h (from easytable_list_times).
typeYesBooking area/type id from easytable_list_types.
emailNoGuest email.
eventNoOptional event id.
mobileYesGuest mobile in E.164 (e.g. +46701234567).
commentNoFree-text note / special requests.
companyNoOptional company name.
personsYesParty size.
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.7
    • changedInput schema / properties / time / description
      Previous value: -"Time slot HH:MM (from easytable_list_times)."New value: +"Time slot HH:MM, 24h (from easytable_list_times)."
    • removedInput schema / properties / time / minLength
      Removed value: -1
    • addedInput schema / properties / time / pattern
      Added value: +"^([01]?\\d|2[0-3]):[0-5]\\d$"
  2. Changed2 schema fields changedv1.2.0
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  3. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed1 schema field changedv0.4.1
    • changedInput schema / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  5. First observedv0.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the first call makes NO network call, confirmation is requested before submitting, and without elicitation support the tool returns a preview plus confirmToken that must be echoed back only after explicit user approval. This is exactly the kind of side-effect and safety sequencing the destructiveHint/idempotentHint annotations cannot express.

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?

Three front-loaded sentences with no filler, and the critical prerequisite and no-network-on-first-call facts come early. Sentences are long and dotted with parentheticals, which slightly hurts scanability but nothing is wasted.

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 destructive, open-world mutation with no output schema, the description covers preconditions, confirmation flow, and the failure/fallback response shape (preview + confirmToken). It does not describe the eventual success response or post-booking behavior, which is a minor gap given no output schema exists.

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 the schema already documents all 13 parameters including field provenance. The description only clarifies confirmToken's role, which is also documented in the schema, so it adds little beyond the structured fields. 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+resource ("Create a restaurant booking") and immediately disambiguates from the modify/cancel/find siblings by describing the create-specific Turnstile/token submission path. An agent can identify the tool's job and scope 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 Guidelines4/5

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

Gives a hard precondition (a loaded book.easytable.com/book/?id=<id> tab must be open) and explains the two-step confirmation path versus the elicitation path, which tells the agent exactly how to sequence calls. It stops short of naming required predecessor siblings like easytable_list_types/dates/times, though the schema references them.

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

Deploy Server

Other Tools