Meet.bot MCP

Book Meeting

book_meeting

Book a new meeting slot

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": {
      "page": "<page>",
      "guest_email": "<guest_email>",
      "guest_name": "<guest_name>",
      "start": "<start>"
    },
    "name": "book_meeting"
  }
}

Input Schema

Name	Required	Description
`page`	Yes	The URL of the scheduling page (e.g. https://meet.bot/your-page)
`notes`	No	Optional notes to include with the meeting (e.g. agenda, call details)
`start`	Yes	Start time in ISO 8601 format (e.g. 2025-03-10T14:00:00Z); must be an available slot
`guest_name`	Yes	Full name of the guest
`guest_email`	Yes	Email address of the guest (used for calendar invite and confirmation)

Schema Changelog

Changes observed during successful MCP inspections.

First observedMar 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states 'Book a new meeting slot' but does not explain side effects (e.g., calendar invite sending), what happens if the slot is taken, or whether the booking is idempotent. This is insufficient for a mutation action.

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 description is a single concise sentence with no filler. It is front-loaded and easy to parse. However, it is so brief that it sacrifices useful behavioral context, but conciseness is not penalized for adding more if the content is already clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with five parameters, no output schema, and no annotations, the description is incomplete. It does not explain the booking workflow, the need for an available slot, or what happens after booking. The sibling get_available_slots implies a dependency but this is not mentioned, leaving the agent without enough context to invoke the tool reliably.

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%, with each parameter having a clear description. The tool description adds no parameter-level detail, but the schema already fully explains the five parameters, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Book a new meeting slot' clearly states the action and object, distinguishing it from siblings like get_available_slots and get_scheduling_pages which are read-only listing tools. It is specific enough to understand the tool's core function, though it could more explicitly tie it to scheduling pages.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisite steps like checking available slots via get_available_slots or failure conditions if the slot is unavailable. The schema hints at 'start must be an available slot' but the description itself gives no usage context.

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

All Meet.bot MCP tools Inspect

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

Need Help?