Skip to main content
Glama
Sign In

TeamMeet

by io.github.theguysaccount
OverviewDiscussionsAdmin

book_time

Book a time on someone's Meetful booking link, for your person. No key needed. Take the time from find_times, and check the time, name and email with your person first. Returns the meeting room link, a calendar file, and a private link to move or cancel; the owner is told an assistant booked it. If the time was taken meanwhile, the error lists the nearest open times.

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, as find_times gave it: "2026-11-12T15:00:00Z" (or with an offset, 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 page's own questions, by question id (find_times lists them).
minutesNoHow long, if the page offers more than one length.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so well: it discloses that no key is needed, that the owner is notified an assistant booked, exactly what is returned (room link, calendar file, private move/cancel link), and the failure behavior when a slot is taken (error lists nearest open times). That is materially more than an agent could infer from the name or schema.

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?

Four short sentences, front-loaded with the action and the no-key fact, then prerequisites, then returns and conflict behavior. No filler or repetition of the schema.

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?

For an 8-parameter mutation tool with no output schema, the description covers side effects, return artifacts, auth, and conflict handling, which is everything an agent needs to call it safely. The nested 'answers' object is at least pointed at find_times for its question ids.

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 3 is the baseline, but the description adds genuine cross-tool meaning by tying 'at' and 'answers' back to find_times output and flagging time, name, and email as the values to confirm with the person. It does not explain 'minutes' or 'about' beyond the schema, keeping it from a 5.

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?

Specific verb+resource ("Book a time on someone's Meetful booking link") plus the object it acts on ("for your person"). It names find_times as the source of the time value, so an agent can immediately place it relative to that sibling without opening either 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 an explicit workflow prerequisite: take the time from find_times and confirm time, name, and email with the person first. There is no explicit when-not-to-use guidance or named alternative for the case where booking is inappropriate, so it falls short of a 5.

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

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