Skip to main content
Glama

Tempi

by com.meettempi
OverviewDiscussionsAdmin

Join the private beta waitlist

join_waitlist

Requests access to host on Tempi (create event types, share a booking page). Not needed to book meetings, since booking pages are public. Returns the status: pending, approved (sign in at APP_URL/login), rejected, or open (no waitlist, sign in directly). Joining again with the same email returns the current status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoa short source tag of lowercase letters, digits, - or _, like "embed"
nameNoa string at most 100 character(s) long
noteNoanything the admins should know, e.g. what you want to use Tempi for
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ref
      Added value: +{
+  "description": "a short source tag of lowercase letters, digits, - or _, like \"embed\"",
+  "pattern": "^[a-z0-9_-]{1,32}$",
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations mark this as a mutating operation (readOnlyHint=false), and the description confirms it by requesting access. It adds valuable behavioral context: the idempotent behavior (joining again returns current status) and the possible return statuses (pending, approved, rejected, open). This goes beyond the basic annotation and helps the agent anticipate results.

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?

The description is four sentences with no filler. The core purpose is front-loaded, followed by a behavioral note and status explanations. Every sentence adds distinct value, and it remains compact despite covering multiple aspects.

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?

There is no output schema, so the description must explain the return values, and it does by listing the possible statuses and their meaning. It also covers the idempotency behavior. Given the tool's simplicity and the annotations, this is complete for an agent to invoke correctly; nothing essential is missing.

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 75% (three of four parameters have descriptions). The description adds semantics for the email parameter by stating that reusing the same email returns the current status, which clarifies its role as the key identifier. For other parameters (ref, name, note), the schema descriptions are sufficient, so the description does not need to elaborate further.

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?

The description states a specific verb ('Requests access to host') and the resource (Tempi hosting capability), and clarifies what it does not do (not needed for booking meetings because pages are public). This clearly distinguishes it from the sibling booking tools, which all deal with bookings and availability.

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 explicitly states when the tool is not needed ('Not needed to book meetings'), giving a clear exclusion. It implies usage when the user wants to become a host, and the sibling list contains no other waitlist tool, so there is no ambiguity about alternatives. The guidance is clear but does not name an alternative tool 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