Skip to main content
Glama

Tempi

by com.meettempi
OverviewDiscussionsAdmin

Find open times

get_available_slots
Read-only

Returns the start times that can be booked, with the hosts' calendars, buffers and limits already applied. Pass the invitee's timezone and either date (YYYY-MM-DD in timezone) or from and to (ISO, at most 62 days apart). With neither, it covers the next 7 days. days groups the slots by date in timezone, and times gives each slot as a local time to show people. People can book up to bookableUntil. When the range has no open times, next is the next one. When timezone was an abbreviation that names more than one zone (CST, IST, BST), timezoneNote says which one was used: check it with the person. For new times for an existing booking, also pass its bookingId and token. Next: call create_booking (or reschedule_booking_as_invitee) with one of the slots values as start.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoend of the range, ISO with an offset
dateNoone day to look at, as YYYY-MM-DD in `timezone`
fromNostart of the range, ISO with an offset
slugYesan event type slug from get_public_profile ("demo" in meettempi.com/acme/demo), or the whole link
tokenNothe token from create_booking, or the manageUrl
handleYesa handle, the first part of a booking link ("acme" in meettempi.com/acme/demo), or the whole link
timezoneYesthe invitee's time zone, an IANA id like America/New_York or an abbreviation like EST: days, dates and times are in it
bookingIdNothe booking id from create_booking, or its manageUrl

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • changedInput schema / properties / bookingId / description
      Previous value: -"a string at least 1 character(s) long"New value: +"the booking id from create_booking, or its manageUrl"
    • removedInput schema / properties / bookingId / minLength
      Removed value: -1
    • removedInput schema / properties / bookingId / title
      Removed value: -"minLength(1)"
    • addedInput schema / properties / date / description
      Added value: +"one day to look at, as YYYY-MM-DD in `timezone`"
    • addedInput schema / properties / from / description
      Added value: +"start of the range, ISO with an offset"
    • 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])?$"
    • 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: days, dates and times are in it"
    • addedInput schema / properties / to / description
      Added value: +"end of the range, ISO with an offset"
    • changedInput schema / properties / token / description
      Previous value: -"a string at least 10 character(s) long"New value: +"the token from create_booking, or the manageUrl"
    • removedInput schema / properties / token / minLength
      Removed value: -10
    • removedInput schema / properties / token / title
      Removed value: -"minLength(10)"
    • changedInput schema / required
      Previous value: -[
-  "handle",
-  "slug"
-]New value: +[
+  "handle",
+  "slug",
+  "timezone"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false), yet the description adds substantial behavior: the 62-day max range, the 7-day default window, ambiguity handling for zone abbreviations via `timezoneNote`, and the `next` fallback when nothing is open. These are constraints and edge cases an agent cannot infer from the read-only annotation.

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?

The purpose is front-loaded in the first sentence and the remaining sentences each carry distinct, load-bearing information (range rules, defaults, abbreviation caveat, next-step routing). It is dense and slightly long, but there is no filler or repetition.

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?

With no output schema, the description carries the full burden of describing return values and does so: `days`, `times`, `bookableUntil`, `next`, `timezoneNote`, and `slots`. Combined with the range defaults, abbreviation caveat and the explicit next-step call, an agent has everything needed to invoke it correctly.

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, but the description adds real semantics beyond the schema: it explains that `date`/`from`/`to` are mutually exclusive modes, that the range is capped at 62 days, and that `timezone` governs the interpretation of days, dates and times. It also clarifies `days`/`times` grouping behavior that the schema does not describe.

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 ('Returns the start times that can be booked') and immediately qualifies scope ('with the hosts' calendars, buffers and limits already applied'). It also routes clearly away from siblings by naming create_booking and reschedule_booking_as_invitee as the follow-up tools, so an agent can place it in the workflow 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 Guidelines4/5

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

Gives concrete context for use: pass `date` or `from`/`to`, defaults to the next 7 days when neither is given, and pass `bookingId`/`token` when looking for new times on an existing booking. It stops short of explicitly stating when NOT to use it versus get_booking or get_public_profile, but the conditions that select each parameter mode are spelled out.

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