Skip to main content
Glama

book_session

Book a one-off session: charge credits (top up via MPP if short), then reserve the chosen Cal slot. Requires Authorization: Bearer. setup_id and start come from get_sessions_or_services and list_session_slots. If credits are short this returns payment_required; pass payment_credential or pay via open_dashboard in the browser, then retry.

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": {
      "setup_id": "<setup_id>",
      "start": "<start>"
    },
    "name": "book_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYes
setup_idYes
payment_credentialNo

Output Schema

NameRequiredDescriptionDefault
endNo
kindNointro_call, mentorship_call, or session.
errorNopayment_required, invalid_payment, auth_required, not_found, etc.
startNo
intentNocharge
methodNostripe
statusNo'paid', 'topped_up', or absent on payment_required.
messageNo
pay_urlNoREST URL to retry with an MPP Payment credential.
receiptNoBase64url MPP receipt.
currencyNousd
setup_idNo
availableNo
challengeNoMPP challenge. Present when error is payment_required.
next_stepNo
amount_usdNoCharge or top-up amount in whole USD.
mentorshipNo
applicationNo
credits_usdNo
billing_noteNo
booking_hashNo
calendar_linkNo
dashboard_urlNo
mentorship_hashNo
application_hashNo
www_authenticateNoWWW-Authenticate Payment header value from the REST 402.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, open-world; the description adds the materially important behavior that this charges credits, requires a Bearer token, and can return payment_required as a recoverable failure. That is real context beyond structured fields. It omits whether a retry after payment_required risks a double charge or whether the call is idempotent, which matters for a credit-consuming mutation.

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: the operation, the auth requirement, then the prerequisite sources and the failure/recovery path, ordered so the agent reads the blocking constraints before the edge case. No filler and 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.

Completeness4/5

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

For a 3-parameter mutating tool that spends credits and can fail on payment, the description covers auth, prerequisites, the payment_required outcome and the retry, and an output schema exists so return values need no explanation. The remaining gap is the format of the start value and any idempotency guarantee on retry.

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 description coverage is 0%, so the description must carry the load, and it does name all three parameters: it identifies the source tools for setup_id and start and explains that payment_credential is supplied only in the short-credits path. It does not specify the expected format of start (e.g. ISO timestamp), which is the one gap on an otherwise fully covered parameter set.

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?

States a specific verb and resource ("Book a one-off session") plus the two internal steps that constitute the operation: charging credits and reserving the Cal slot. The qualifier "one-off session" distinguishes it from the sibling book_intro_call and book_mentorship_call without needing to open 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 prerequisite chain: setup_id comes from get_sessions_or_services and start from list_session_slots, so the agent knows what must be called first. It also prescribes the recovery path when credits are short (pass payment_credential, pay via open_dashboard, retry). It stops short of explicitly excluding the intro-call and mentorship-call booking siblings, leaving that to the word "one-off".

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.

Resources