Skip to main content
Glama

book_mentorship_call

Book a mentorship call on an active mentorship. Requires Authorization: Bearer. start is an ISO-8601 datetime from list_mentorship_call_slots.

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": {
      "mentorship_hash": "<mentorship_hash>",
      "start": "<start>"
    },
    "name": "book_mentorship_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYes
mentorship_hashYes

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

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds the auth requirement (Bearer token) and the precondition that the mentorship must be active, which is real value. It omits side effects an agent would care about—whether credits are charged, whether the booking is confirmed immediately, or what happens on slot conflict.

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 short sentences, front-loaded with the action, then the auth prerequisite, then the key parameter constraint. No filler or restatement of the name.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the auth prerequisite is covered. For a two-parameter mutation with zero schema coverage, however, the unexplained 'mentorship_hash' and the silence on credit/cost and failure behavior leave real gaps.

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 0%, so the description must carry the load. It does well on 'start' (ISO-8601, sourced from list_mentorship_call_slots) but adds nothing about 'mentorship_hash' beyond the phrase 'active mentorship'—no format, source, or where to obtain it.

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 names a specific verb and resource ('Book a mentorship call') and constrains it to an 'active mentorship', which separates it from intro-call or session booking siblings. It does not explicitly name those siblings, so differentiation is inferred rather than stated.

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?

'start is an ISO-8601 datetime from list_mentorship_call_slots' explicitly routes the agent to the sibling tool that supplies valid inputs, which is concrete when-to-use guidance. It lacks exclusions (e.g., when not to book, or what to do if no active mentorship exists), so it stops short of full guidance.

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