Skip to main content
Glama

schedule_session

Book a session for a client (confirm-gated). Pass the client's active subscriptionId when they have one (see list_subscriptions) so it counts against their plan's sessions; omit it for intro/one-off calls or clients without a plan — the coach can still book. Times are ISO strings.

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": {
      "clientId": "<clientId>",
      "scheduledStart": "<scheduledStart>",
      "scheduledEnd": "<scheduledEnd>"
    },
    "name": "schedule_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoONLINE
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
clientIdYes
meetingLinkNo
scheduledEndYes
scheduledStartYes
subscriptionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "clientId",
      -  "subscriptionId",
      -  "scheduledStart",
      -  "scheduledEnd"
      -]New value: +[
      +  "clientId",
      +  "scheduledStart",
      +  "scheduledEnd"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already establish write/non-destructive/non-openWorld, and the description adds useful behavior: booking is gated behind confirm and a missing subscriptionId still permits the booking. It does not disclose side effects an agent would care about — whether the client is notified, how double-booking or overlapping times are handled, or what the preview actually returns.

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 tight sentences with no padding; the gating caveat and the primary action are front-loaded, and the subscriptionId rule follows in the order an agent would need to apply it.

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 7-parameter mutation with no output schema, the definition covers the essentials: what it creates, the confirm gate, and the subscription linkage. It would be stronger if it noted whether meetingLink is required for ONLINE sessions or what the preview response contains.

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?

With schema description coverage at only 14%, the description carries real weight and does so for the highest-risk parameter: it explains subscriptionId's meaning and when to supply or omit it, and states that times are ISO strings for scheduledStart/scheduledEnd. It leaves the type enum (IN_PERSON/ONLINE) and meetingLink's relationship to online sessions unexplained, so coverage is good but not complete.

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 — 'Book a session for a client' — plus the '(confirm-gated)' qualifier, so an agent immediately knows the operation and its gating behavior. It does not explicitly say how it differs from siblings such as book_session_for_groups or reschedule_session, so sibling differentiation is only implied by 'for a client'.

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 gives a clear conditional rule: pass subscriptionId when the client has an active plan, omit it for intro/one-off calls or clients without a plan, and it routes the agent to list_subscriptions to find that ID. It also signals the confirm-gated flow. What's missing is when to pick this tool over reschedule_session or the group-booking variants, but the in-tool usage context is solid.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.