Skip to main content
Glama

book_intro_call

Book an intro call on an accepted application. Requires Authorization: Bearer. start is an ISO-8601 datetime from list_intro_call_slots. Does not retry other slots on failure.

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": {
      "application_hash": "<application_hash>",
      "start": "<start>"
    },
    "name": "book_intro_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYes
application_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

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), it discloses the auth requirement ('Authorization: Bearer') and a genuinely non-obvious behavior: it will not fall back to another slot on failure, so a failed booking leaves the agent to retry deliberately. It does not say what failure looks like or whether a slot is held during the call.

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 precondition, then auth, then the input source, then the failure caveat. No sentence is filler.

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 safety profile is covered by annotations. Still missing for a booking mutation: what happens to credits or cost (siblings like pay_application and top_up_credits hint at a paid flow), whether repeated calls double-book, and what a failure response indicates. Adequate but with 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 description coverage is 0%, so both parameters rely on the description. 'start' is well served (ISO-8601, sourced from list_intro_call_slots), but 'application_hash' gets only the indirect hint that it refers to an accepted application — no format or provenance is given, so half the surface remains unstated.

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?

The description states a specific verb and resource ('Book an intro call') and narrows the scope to 'an accepted application', which separates it from booking a mentorship call or a session. An agent can tell what this tool does without opening the 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?

It gives a clear precondition (the application must already be accepted) and routes the agent to list_intro_call_slots as the source of valid 'start' values. It stops short of naming when to prefer book_mentorship_call or book_session instead, so guidance is strong but not exhaustive.

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