Skip to main content
Glama

Tempi

by com.meettempi
OverviewDiscussionsAdmin

Check a repeating series before booking it

check_series
Read-only

For event types with repeatMax (from get_public_profile): lists each meeting of a series that starts at start (one of the slots) and repeats every 1, 2 or 4 weeks at the host's clock time, and whether each is free. Pass the invitee's timezone to get each meeting's when in it: where clocks change on other dates than the host's, some meetings move for the invitee, and message says which. Book it with create_booking and repeat when bookable is true. A series is booked whole or not at all, and round robin gives every meeting to the same host.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesan event type slug from get_public_profile ("demo" in meettempi.com/acme/demo), or the whole link
countYeshow many meetings, first included (2 up to the event type's repeatMax)
everyYesweeks between meetings: 1, 2 or 4
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
timezoneNothe invitee's time zone, an IANA id like America/New_York or an abbreviation like EST: each meeting's `when` is in it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / count / description
      Added value: +"how many meetings, first included (2 up to the event type's repeatMax)"
    • addedInput schema / properties / every / description
      Added value: +"weeks between meetings: 1, 2 or 4"
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "the invitee's time zone, an IANA id like America/New_York or an abbreviation like EST: each meeting's `when` is in it",
+  "type": "string"
+}
  2. Changed10 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
-  "NumberFromString": {
-    "description": "a string to be decoded into a number",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / count / $ref
      Removed value: -"#/$defs/NumberFromString"
    • addedInput schema / properties / count / anyOf
      Added value: +[
+  {
+    "description": "how many meetings, first included (2 up to the event type's repeatMax)",
+    "maximum": 52,
+    "minimum": 2,
+    "title": "between(2, 52)",
+    "type": "integer"
+  },
+  {
+    "description": "a string to be decoded into a number",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / every / $ref
      Removed value: -"#/$defs/NumberFromString"
    • addedInput schema / properties / every / anyOf
      Added value: +[
+  {
+    "description": "weeks between meetings: 1, 2 or 4",
+    "enum": [
+      1,
+      2,
+      4
+    ],
+    "type": "number"
+  },
+  {
+    "description": "a string to be decoded into a number",
+    "type": "string"
+  }
+]
    • 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])?$"
    • 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)"
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safe-read profile, and the description adds substantial behavior beyond them: a series is atomic ('booked whole or not at all'), round robin pins all meetings to one host, and clocks changing on other dates can move some meetings for the invitee with `message` explaining which. This is exactly the extra context annotations cannot convey.

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?

Every sentence carries load: capability, timezone/DST semantics, booking hand-off, and atomicity/round-robin behavior. It is dense but front-loaded with the what, then the how, then the caveats, with no filler.

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, read-only tool with no output schema, the description explains the returned concepts (`when`, `bookable`, `message`) and the constraints an agent needs before calling, including the atomic-booking and round-robin consequences.

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 schema already documents all six parameters (baseline 3). The description still adds real meaning: `every` repeats 'at the host's clock time', `start` must be one of the slots, `timezone` shifts each meeting's `when` and can move it on DST dates, and `count` is bounded by the event type's repeatMax.

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 (lists/checks) and resource (each meeting of a repeating series), plus the exact scope: starts at `start`, repeats `every` 1/2/4 weeks, reports free/busy per meeting. An agent can distinguish this from get_available_slots and create_booking without opening a 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?

Gives the precondition ('For event types with `repeatMax` from get_public_profile'), the follow-up action and its condition ('Book it with create_booking and `repeat` when `bookable` is true'), and implicitly routes non-repeating cases elsewhere. Alternatives are named explicitly.

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