Skip to main content
Glama

Tempi

by com.meettempi
OverviewDiscussionsAdmin

Book a meeting

create_booking

Books start, which must be one of the slots from get_available_slots. Free events are confirmed at once, unless the event type has requiresApproval: then it's a request (status=pending_approval) that holds the time until a host approves or declines it, and the invitee hears either way by email. Nobody answering by its start (holdExpiresAt) lets it lapse. Tell the human it isn't confirmed yet. Paid events return status=pending_payment and a paymentUrl. Give it to the human to pay before holdExpiresAt, or the slot is released. Once confirmed, the event is added to the host's calendar if they connected one, and the invitee gets a confirmation email with a calendar file (.ics). Keep manageUrl and token: they are the only way to view, reschedule or cancel later. 409 slot_unavailable says why the time can't be booked and lists the nearest open times. The result's when is the start in the invitee's time zone, to tell them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesthe invitee's full name
slugYesan event type slug from get_public_profile ("demo" in meettempi.com/acme/demo), or the whole link
coverNoleave it out: the id of the painting the booking page showed, when the event type shows a different one each booking (cover "hand", "light" or "still"), so the booking keeps it. Anything else is ignored, and Tempi picks one
emailYesthe invitee's email address, which gets the confirmation and its calendar file
notesNoanything the invitee wants the host to know
phoneNothe invitee's phone number with its country code, like +1 415 555 0134: required when the event type is a phone call (whereKind phone on get_public_profile), where the host calls them
startYesone of the `slots` values from get_available_slots, as given (ISO in UTC)
handleYesa handle, the first part of a booking link ("acme" in meettempi.com/acme/demo), or the whole link
repeatNobook a series instead: `count` meetings, `every` 1, 2 or 4 weeks at the host's clock time, when the event type's repeatMax allows. All or nothing: check_series first. The result's `series.meetings` give each start as `when` in the invitee's time zone, and `series.clockNote` says when that moves
timezoneYesthe invitee's time zone, an IANA id like America/New_York or an abbreviation like EST: their emails and reminders show times in it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"the invitee's email address, which gets the calendar invitation"New value: +"the invitee's email address, which gets the confirmation and its calendar file"
  2. Changed1 schema field changed
    • addedInput schema / properties / phone
      Added value: +{
+  "description": "the invitee's phone number with its country code, like +1 415 555 0134: required when the event type is a phone call (whereKind phone on get_public_profile), where the host calls them",
+  "maxLength": 40,
+  "minLength": 0,
+  "title": "maxLength(40)",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / cover
      Added value: +{
+  "description": "leave it out: the id of the painting the booking page showed, when the event type shows a different one each booking (cover \"hand\", \"light\" or \"still\"), so the booking keeps it. Anything else is ignored, and Tempi picks one",
+  "maxLength": 40,
+  "title": "maxLength(40)",
+  "type": "string"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / repeat / description
      Previous value: -"book a series instead: `count` meetings, `every` 1, 2 or 4 weeks at the same local time, when the event type's repeatMax allows. All or nothing: check_series first"New value: +"book a series instead: `count` meetings, `every` 1, 2 or 4 weeks at the host's clock time, when the event type's repeatMax allows. All or nothing: check_series first. The result's `series.meetings` give each start as `when` in the invitee's time zone, and `series.clockNote` says when that moves"
  5. Changed13 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
-  "Trim": {
-    "description": "a string that will be trimmed",
-    "type": "string"
-  }
-}
    • addedInput schema / properties / email / description
      Added value: +"the invitee's email address, which gets the calendar invitation"
    • changedInput schema / properties / handle / description
      Previous value: -"1-40 lowercase letters, digits or dashes, starting and ending with a letter or digit"New value: +"a handle, the first part of a booking link (\"acme\" in meettempi.com/acme/demo), or the whole link"
    • removedInput schema / properties / handle / pattern
      Removed value: -"^[a-z0-9](?:[a-z0-9-]{0,38}[a-z0-9])?$"
    • removedInput schema / properties / name / $ref
      Removed value: -"#/$defs/Trim"
    • addedInput schema / properties / name / description
      Added value: +"the invitee's full name"
    • addedInput schema / properties / name / type
      Added value: +"string"
    • changedInput schema / properties / notes / description
      Previous value: -"a string at most 2000 character(s) long"New value: +"anything the invitee wants the host to know"
    • changedInput schema / properties / slug / description
      Previous value: -"1-40 lowercase letters, digits or dashes, starting and ending with a letter or digit"New value: +"an event type slug from get_public_profile (\"demo\" in meettempi.com/acme/demo), or the whole link"
    • removedInput schema / properties / slug / pattern
      Removed value: -"^[a-z0-9](?:[a-z0-9-]{0,38}[a-z0-9])?$"
    • addedInput schema / properties / start / description
      Added value: +"one of the `slots` values from get_available_slots, as given (ISO in UTC)"
    • changedInput schema / properties / timezone / description
      Previous value: -"an IANA time zone such as \"America/New_York\""New value: +"the invitee's time zone, an IANA id like America/New_York or an abbreviation like EST: their emails and reminders show times in it"
    • changedInput schema / required
      Previous value: -[
-  "handle",
-  "slug",
-  "start",
-  "name",
-  "email"
-]New value: +[
+  "handle",
+  "slug",
+  "start",
+  "name",
+  "email",
+  "timezone"
+]
  6. Changed3 schema fields changed
    • addedInput schema / properties / name / $ref
      Added value: +"#/$defs/Trim"
    • removedInput schema / properties / name / allOf
      Removed value: -[
-  {
-    "$ref": "#/$defs/Trim"
-  }
-]
    • removedInput schema / properties / name / description
      Removed value: -"the invitee's full name"
  7. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=false; the description carries the real behavior burden and discloses it richly: pending_approval holds, holdExpiresAt lapse, pending_payment + paymentUrl, slot release on non-payment, host-calendar insertion, confirmation email with .ics, and the 409 slot_unavailable error with `nearest` alternatives. This is far beyond what annotations provide.

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 core action and the slot constraint, then ordered by outcome (free → approval → paid → confirmed → error). The single dense paragraph wastes almost nothing, though the output/return-value detail (manageUrl, token, series.meetings, `when`) makes it long and would read better split into labeled sentences against the missing output schema.

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?

No output schema exists, and the description compensates fully: it names the returned statuses, paymentUrl, manageUrl/token (and warns they are the only way to manage later), `when` in the invitee's time zone, series.meetings/clockNote, and the 409 nearest list. Combined with 10 parameters and a nested `repeat` object, an agent has everything needed to invoke 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% and the schema already documents `start`, `timezone`, `slug`, `handle`, `phone`, `repeat` in detail, so the baseline is 3. The description reinforces rather than adds: it repeats that `start` must be one of the get_available_slots values and that `timezone` drives email display, both of which the schema already states. No new syntax or format guidance beyond the structured fields.

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?

Opens with a specific verb+resource ("Books `start`") and immediately pins the value to a source (slots from get_available_slots), which is exactly the ambiguity for a booking tool. It is clearly distinguishable from its siblings (cancel/reschedule_as_invitee, check_series), several of which it names or implicitly routes to.

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?

It routes the agent explicitly: `start` must come from get_available_slots, and series bookings must go through check_series first ("All or nothing: check_series first"). It also gives the branch conditions (requiresApproval, paid events). It stops short of an explicit "do not use this when…" rule or a named alternative for one-off vs series beyond check_series.

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

All Tempi 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