Skip to main content
Glama
Sign In

Meetful

by com.meetful
OverviewDiscussionsAdmin

Set up a booking page

set_up_booking_page
DestructiveIdempotent

Creates a Meetful booking page (meetful.com/) and returns the code to put it on a website: a one-line button, the page inline, an iframe, or a plain link. Every booking gets its own video room. For a signed-in person the page is theirs and live at once; otherwise the result includes a claim link, and the page goes live when its owner signs in.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "set_up_booking_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesWhose booking page this is — shown on it.
siteNoThe website it goes on — shown to the person when they claim it.
blurbNoA sentence or two under the heading.
emailNoThe person's address — shown on the claim page so they know it was made for them. Nothing is sent to it.
hoursNoOpen hours, like "Mon-Fri 09:00-17:00" or "Mon-Thu 9am-5pm; Fri 9am-1pm". Default Monday to Friday, 9 to 5.
titleNoThe page's heading, like "Book a call with Ada".
handleNoThe address wanted: meetful.com/<handle>. Optional — one is made from the name.
lengthsNoHow long a meeting can be, in minutes — any of 15, 30, 45, 60, 90. The person booking picks one; the first is shown first. Default 30.
timezoneNoIANA time zone the hours are in, like America/New_York.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=true, readOnlyHint=false, yet the description adds real behavioural context they don't carry: the page is live immediately for a signed-in person, otherwise a claim link is returned and the page activates on sign-in, and every booking gets its own video room. It does not explain the destructive or idempotent hints (e.g. whether reusing a handle overwrites an existing page), which is the main remaining gap.

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?

Three sentences, front-loaded with verb and resource, then return value, then the signed-in/claim nuance. No filler, no restatement of the title, and each sentence carries information the agent needs.

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 nine-parameter creation tool with no output schema, the description does the important extra work of explaining what is returned (embed code variants, or a claim link) and how the page becomes live. It stops short of covering idempotency behaviour and handle-reuse conflicts implied by the annotations.

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 all nine parameters including handle, hours and lengths are already documented in the schema, which sets the baseline at 3. The description adds only mild context by showing the handle's URL shape; it contributes no semantics about defaults, handle collisions, or timezone interaction that isn't already structured.

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 first sentence gives a specific verb (creates), a specific resource (a Meetful booking page at meetful.com/<handle>), and the concrete return value (embed code in four flavours). An agent knows exactly what it gets back without opening the schema, and the scope is narrow enough to distinguish it from status/booking siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: it's the tool you call to create a page, and the signed-in vs anonymous outcome is described. However, there is no explicit when-to-use vs when-not guidance, no mention of using booking_page_status to check an existing page first, and no note on what happens if a handle is already taken.

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

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