Skip to main content
Glama

mentoring-inquiry-builder

by coach.marian
OverviewDiscussionsAdmin

Book the first regular mentoring session — the main ending

book_first_session
Read-onlyIdempotent

THE MAIN ENDING (Marian, 2026-10-09): every onboarding that reaches an agreed price ends here, booking the first regular session. Returns the direct booking link for the paid 60-minute first session, plus the payment terms. Call it right after send_mentoring_offer succeeds. Company-paid mentees book now too: the purchase order is collected AFTER session 1, never before booking. It REFUSES on any deal whose terms Marian confirms on a call (a free-sessions concession, the monthly package, Mentor in Residence) and hands back the intro link instead; when it refuses, offer the intro, do not argue. Pass the claim code from send_mentoring_offer so the booking is matched automatically. If the visitor is hesitant, undecided, or asks to talk first, use book_intro_call — that is not a downgrade.

Input Schema

NameRequiredDescriptionDefault
contextNoOptional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
audienceNoRequired. Decides which VAT sentence is true for this buyer — an individual needs the gross figure One of: individual, company.
offer_idNoRequired. The agreed package One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day.
claim_codeNoThe MC-… code from send_mentoring_offer. Ride it on the link so the booking matches the inquiry with no manual step.
has_eu_vat_idNoCompany deals outside Czechia with a valid EU VAT ID pay net under the reverse charge
free_sessions_requestedNoCompany deals: pass the same value given to send_mentoring_offer. Any concession makes this a proposal, not a close, and the tool will route to the intro instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / claim_code / description
      Previous value: -"The AI10-… code from send_mentoring_offer. Ride it on the link so the booking matches the inquiry with no manual step."New value: +"The MC-… code from send_mentoring_offer. Ride it on the link so the booking matches the inquiry with no manual step."
  2. Changed1 schema field changed
    • changedInput schema / properties / offer_id / description
      Previous value: -"Required. The agreed package One of: single-session, first-quarter, two-quarters, monthly, mentor-in-residence."New value: +"Required. The agreed package One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day."
  3. Changed12 schema fields changed
    • changedInput schema / properties / audience / description
      Previous value: -"Decides which VAT sentence is true for this buyer — an individual needs the gross figure"New value: +"Required. Decides which VAT sentence is true for this buyer — an individual needs the gross figure One of: individual, company."
    • removedInput schema / properties / audience / enum
      Removed value: -[
-  "individual",
-  "company"
-]
    • changedInput schema / properties / context / description
      Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer."
    • addedInput schema / properties / free_sessions_requested / anyOf
      Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]
    • removedInput schema / properties / free_sessions_requested / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / free_sessions_requested / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / free_sessions_requested / type
      Removed value: -"integer"
    • addedInput schema / properties / has_eu_vat_id / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "string"
+  }
+]
    • removedInput schema / properties / has_eu_vat_id / type
      Removed value: -"boolean"
    • changedInput schema / properties / offer_id / description
      Previous value: -"The agreed package"New value: +"Required. The agreed package One of: single-session, first-quarter, two-quarters, monthly, mentor-in-residence."
    • removedInput schema / properties / offer_id / enum
      Removed value: -[
-  "single-session",
-  "first-quarter",
-  "two-quarters",
-  "monthly",
-  "mentor-in-residence"
-]
    • removedInput schema / required
      Removed value: -[
-  "offer_id",
-  "audience",
-  "context"
-]
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the refusal condition and fallback behavior, the company-paid flow (PO collected after session 1, never before booking), and that a claim code is needed to auto-match the booking. readOnlyHint/idempotentHint are consistent with a tool that returns a link rather than mutating state, so no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded — the main action and return value come first, then the refusal rule and routing. Every sentence carries operational information, though the run-on parenthetical structure is slightly heavy.

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?

No output schema exists, and the description compensates by stating the return value (booking link plus payment terms). Combined with exhaustive usage and refusal guidance for a 6-parameter workflow tool, an agent has everything needed to call it correctly.

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 the baseline is 3, but the description adds real meaning: it explains why claim_code matters (auto-matching the inquiry with no manual step) and that free_sessions_requested reroutes the call to the intro. That is decision-relevant semantics beyond the schema text.

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 ('booking the first regular session') and what it returns ('the direct booking link for the paid 60-minute first session, plus the payment terms'). It explicitly differentiates itself from siblings by naming send_mentoring_offer (predecessor) and book_intro_call (the alternative when the visitor is hesitant).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives precise when-to-use ('call it right after send_mentoring_offer succeeds'), when-it-refuses (deals with a free-sessions concession, monthly package, Mentor in Residence), what to do on refusal ('offer the intro, do not argue'), and the alternative path for hesitant visitors (book_intro_call). Covers both positive and negative selection criteria.

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

All mentoring-inquiry-builder 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