Skip to main content
Glama

mentoring-inquiry-builder

by coach.marian
OverviewDiscussionsAdmin

Book the free 30-minute intro call

book_intro_call
Read-onlyIdempotent

THE FALLBACK for anyone who has not decided (the main ending is book_first_session once the price is agreed). A direct booking link for the free 30-minute intro with Marian. Offer it on hesitation, on a price objection, when the visitor cannot name their problem, after an error, and to anyone who wants to talk before paying. It is never a downgrade, and a booked call from an undecided visitor beats a package they picked at random. Booking it is NOT a condition of the channel rate — never say it is. For a visitor who has already agreed the price on an eligible package, use book_first_session instead: they have decided, and sending them to an intro adds a step they did not ask for. Pass offer_id if one has been chosen so the pricing language is correct.

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.
offer_idNoThe package under discussion, if any — the CTA then repeats that package's published price. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / offer_id / description
      Previous value: -"The package under discussion, if any — conditions the discount wording. Without it the tool cannot tell whether booking locks a discount, and a single-session buyer used to be told it did. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day."New value: +"The package under discussion, if any — the CTA then repeats that package's published price. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day."
  2. Changed1 schema field changed
    • changedInput schema / properties / offer_id / description
      Previous value: -"The package under discussion, if any — conditions the discount wording. Without it the tool cannot tell whether booking locks a discount, and a single-session buyer used to be told it did. One of: single-session, first-quarter, two-quarters, monthly, mentor-in-residence."New value: +"The package under discussion, if any — conditions the discount wording. Without it the tool cannot tell whether booking locks a discount, and a single-session buyer used to be told it did. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day."
  3. Changed4 schema fields changed
    • 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."
    • changedInput schema / properties / offer_id / description
      Previous value: -"The package under discussion, if any — conditions the discount wording. Without it the tool cannot tell whether booking locks a discount, and a single-session buyer used to be told it did."New value: +"The package under discussion, if any — conditions the discount wording. Without it the tool cannot tell whether booking locks a discount, and a single-session buyer used to be told it did. 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: -[
-  "context"
-]
  4. Changed1 schema field changed
    • changedInput schema / properties / offer_id / enum
      Previous value: -[
-  "single-session",
-  "first-quarter",
-  "monthly",
-  "mentor-in-residence"
-]New value: +[
+  "single-session",
+  "first-quarter",
+  "two-quarters",
+  "monthly",
+  "mentor-in-residence"
+]
  5. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "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.\"",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "context"
+]
  6. Changed1 schema field changed
    • addedInput schema / properties / offer_id
      Added value: +{
+  "description": "The package under discussion, if any — conditions the discount wording. Without it the tool cannot tell whether booking locks a discount, and a single-session buyer used to be told it did.",
+  "enum": [
+    "single-session",
+    "first-quarter",
+    "monthly",
+    "mentor-in-residence"
+  ],
+  "type": "string"
+}
  7. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds non-annotation context: that the call is 'never a downgrade,' that booking is NOT a condition of the channel rate, and that offer_id shapes the pricing language in the CTA. It does not discuss auth or rate limits, but for a read-only link generator this is appropriately rich.

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?

It is front-loaded with 'THE FALLBACK' and the core action sentence comes immediately, which is good structure. The list of trigger scenarios is somewhat verbose and partially overlapping ('on hesitation' vs. 'to anyone who wants to talk before paying'), costing some efficiency but not readability.

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?

With only 2 optional parameters, full schema coverage, and annotations carrying the safety profile, the description covers selection, routing, and even the return behavior ('A direct booking link' whose CTA echoes the package price). It is essentially complete; only minor duplication keeps it from a 5.

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 100%, so the baseline is 3. The description's note to 'Pass offer_id if one has been chosen so the pricing language is correct' adds the rationale and the condition for passing it, but largely restates what the schema already documents. No syntax or format details are added beyond that.

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+resource: 'A direct booking link for the free 30-minute intro with Marian.' It also explicitly distinguishes itself from its closest sibling, naming book_first_session as the 'main ending' while positioning this tool as 'THE FALLBACK.' An agent can route correctly without opening 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 Guidelines5/5

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

It enumerates precise trigger conditions ('on hesitation, on a price objection, when the visitor cannot name their problem, after an error, and to anyone who wants to talk before paying') and an explicit when-not: for a visitor who has already agreed the price on an eligible package, use book_first_session instead. It even gives the reasoning for the exclusion.

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