Skip to main content
Glama
Sign In

Meetful

by com.meetful
OverviewDiscussionsAdmin

Book a time

book_time

Books a time on someone's Meetful booking link for the person using the assistant. Returns the meeting link, a calendar file and a private link to move or cancel; the owner is told an assistant made the booking. If the time was taken meanwhile, the error lists the nearest open times. No sign-in needed.

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": {
      "link": "<link>",
      "at": "<at>",
      "name": "<name>"
    },
    "name": "book_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesThe start time, in ISO 8601 (like 2026-11-12T15:00:00Z) or epoch milliseconds.
viaNoYour own name (Grok, ChatGPT, Claude…), so the owner knows which assistant booked.
linkYesThe booking link, or just the name in it.
nameYesWho will be in the meeting — your person's name.
aboutNoWhat they want to cover. It becomes the first item in the meeting.
emailNoTheir email: the confirmation, the calendar file and the link to move it go there. Recommended.
answersNoAnswers to the booking page's own questions, by question id.
minutesNoHow long, if the page offers more than one length.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare this is a non-readonly, non-idempotent, open-world write, so the bar is lower, yet the description still adds real value: it discloses the side effect that the owner is told an assistant made the booking, the exact return artifacts (meeting link, calendar file, private move/cancel link), and the conflict path where the error lists nearest open times.

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?

A single tight paragraph front-loads the action, then covers returns, failure behavior, and auth in descending order of importance. Every sentence carries distinct information with no restatement of the name or title.

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 eight parameters, a nested object, and no output schema, the description compensates by enumerating the return values and the error behavior. An agent knows what it gets back and what happens on a race condition, which is the main missing structured information.

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 the baseline is 3 and the schema already explains every parameter including the nested answers object. The description adds only indirect meaning, such as the conflict-avoidance framing of "at" and the transparency purpose behind "via," without documenting formats or constraints itself.

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 opens with a specific verb and resource: "Books a time on someone's Meetful booking link for the person using the assistant." That clearly separates it from setup/discovery siblings like set_up_booking_page and find_times, though it never names those alternatives explicitly.

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 context is implied rather than stated: the agent books on behalf of "the person using the assistant," and "No sign-in needed" removes an auth prerequisite. There is no explicit when-to-use versus find_times, and no stated preconditions such as needing a confirmed time first.

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