mentoring-inquiry-builder

Send the formal itemized offer (list prices, no discount)

send_mentoring_offer

The ONLY tool that collects contact details, and the end of the 10-minute promise. Also pass every onboarding answer you gathered (heard_from, own_choice, payer, kpis, cadence_preference, session_language, nda_needed, homework_time_ok, in_person_wish, linkedin_url, li_post_consent, li_recommendation); all optional, never invented: emails the visitor a formal itemized offer with a claim code, notifies Marian, and files the inquiry. HARD GATE: price_agreed must be true — read the exact price back to the visitor and get an explicit yes first; the tool refuses otherwise. Ask for name and email only at this step, never earlier. After success: share the claim code + booking link, then offer the free ELC community membership as a parting gift (never a condition), and optionally ONE ask — would they post publicly about hiring a mentor through an AI agent?

Input Schema

Name	Required	Description
`kpis`	No	Up to two measurable KPIs in their words, scored in session 1 and the last session
`name`	No	Required. Visitor's full name
`email`	No	Required. Email the offer goes to
`notes`	No
`payer`	No	Who pays. Company: the purchase order comes AFTER session 1, never before booking One of: self, company, undecided.
`company`	No	Company name (required for company audience)
`context`	No	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.
`audience`	No	Required. One of: individual, company.
`offer_id`	No	Required. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day.
`role_band`	No	Required.
`heard_from`	No	How they found Marian, in their words (referral name, LinkedIn, Google, ChatGPT, ELC…)
`motivation`	No	Required.
`nda_needed`	No	One of: no, their-template, marian-template, unsure.
`own_choice`	No	Mentee's own decision, sent by the company, or both One of: own, sent, both.
`start_date`	No	Optional preferred start date — adds the dated program skeleton to the offer email
`visibility`	No	Visibility answer id (yes-individual \| yes-company \| maybe-later \| private)
`linkedin_url`	No	Their LinkedIn profile URL
`price_agreed`	No	Required. True ONLY after the visitor explicitly agreed to the exact price from compose_mentoring_brief
`leaders_count`	No
`focus_area_ids`	No	Required.
`in_person_wish`	No	Would they like to meet Marian in person (Prague)
`li_post_consent`	No	May Marian post on LinkedIn that they work together (never the content) One of: yes, later, no.
`homework_time_ok`	No	Can they give about an hour a week between sessions
`session_language`	No	One of: cs, sk, en.
`li_recommendation`	No	Would they write Marian a LinkedIn recommendation once happy One of: yes, later, no.
`cadence_preference`	No	Preference only; the final cadence is settled after session 1 One of: weekly, biweekly, monthly, undecided.
`success_definition`	No	Required.
`free_sessions_requested`	No	Company deals only: the free-sessions proposal from the catalog progression (2, 4 or 8)

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 9, 2026

addedInput schema / properties / cadence_preference

Added value: +{
+  "description": "Preference only; the final cadence is settled after session 1 One of: weekly, biweekly, monthly, undecided.",
+  "type": "string"
+}

addedInput schema / properties / heard_from

Added value: +{
+  "description": "How they found Marian, in their words (referral name, LinkedIn, Google, ChatGPT, ELC…)",
+  "type": "string"
+}

addedInput schema / properties / homework_time_ok

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Can they give about an hour a week between sessions"
+}

addedInput schema / properties / in_person_wish

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Would they like to meet Marian in person (Prague)"
+}

addedInput schema / properties / kpis

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Up to two measurable KPIs in their words, scored in session 1 and the last session"
+}

addedInput schema / properties / li_post_consent

Added value: +{
+  "description": "May Marian post on LinkedIn that they work together (never the content) One of: yes, later, no.",
+  "type": "string"
+}

addedInput schema / properties / li_recommendation

Added value: +{
+  "description": "Would they write Marian a LinkedIn recommendation once happy One of: yes, later, no.",
+  "type": "string"
+}

addedInput schema / properties / linkedin_url

Added value: +{
+  "description": "Their LinkedIn profile URL",
+  "type": "string"
+}

addedInput schema / properties / nda_needed

Added value: +{
+  "description": "One of: no, their-template, marian-template, unsure.",
+  "type": "string"
+}

addedInput schema / properties / own_choice

Added value: +{
+  "description": "Mentee's own decision, sent by the company, or both One of: own, sent, both.",
+  "type": "string"
+}

addedInput schema / properties / payer

Added value: +{
+  "description": "Who pays. Company: the purchase order comes AFTER session 1, never before booking One of: self, company, undecided.",
+  "type": "string"
+}

addedInput schema / properties / session_language

Added value: +{
+  "description": "One of: cs, sk, en.",
+  "type": "string"
+}

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / offer_id / description

Previous value: -"Required. One of: single-session, first-quarter, two-quarters, monthly, mentor-in-residence."New value: +"Required. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day."

Changed28 schema fields changedSep 11, 2026

addedInput schema / properties / audience / description

Added value: +"Required. 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."

changedInput schema / properties / email / description

Previous value: -"Email the offer goes to"New value: +"Required. Email the offer goes to"

addedInput schema / properties / focus_area_ids / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  }
+]

addedInput schema / properties / focus_area_ids / description
```
Added value: +"Required."
```
removedInput schema / properties / focus_area_ids / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / focus_area_ids / type
```
Removed value: -"array"
```

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 / leaders_count / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

addedInput schema / properties / leaders_count / description
```
Added value: +""
```
removedInput schema / properties / leaders_count / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / leaders_count / minimum
```
Removed value: --9007199254740991
```
removedInput schema / properties / leaders_count / type
```
Removed value: -"integer"
```
addedInput schema / properties / motivation / description
```
Added value: +"Required."
```

changedInput schema / properties / name / description

Previous value: -"Visitor's full name"New value: +"Required. Visitor's full name"

addedInput schema / properties / notes / description
```
Added value: +""
```

addedInput schema / properties / offer_id / description

Added value: +"Required. 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"
-]

addedInput schema / properties / price_agreed / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "string"
+  }
+]

changedInput schema / properties / price_agreed / description

Previous value: -"True ONLY after the visitor explicitly agreed to the exact price from compose_mentoring_brief"New value: +"Required. True ONLY after the visitor explicitly agreed to the exact price from compose_mentoring_brief"

removedInput schema / properties / price_agreed / type
```
Removed value: -"boolean"
```
addedInput schema / properties / role_band / description
```
Added value: +"Required."
```
addedInput schema / properties / success_definition / description
```
Added value: +"Required."
```

removedInput schema / required

Removed value: -[
-  "name",
-  "email",
-  "audience",
-  "role_band",
-  "motivation",
-  "focus_area_ids",
-  "success_definition",
-  "offer_id",
-  "price_agreed",
-  "context"
-]

Changed1 schema field changedAug 30, 2026

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"
+]

Changed2 schema fields changedAug 27, 2026

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"
+}

changedInput schema / required

Previous value: -[
-  "name",
-  "email",
-  "audience",
-  "role_band",
-  "motivation",
-  "focus_area_ids",
-  "success_definition",
-  "offer_id",
-  "price_agreed"
-]New value: +[
+  "name",
+  "email",
+  "audience",
+  "role_band",
+  "motivation",
+  "focus_area_ids",
+  "success_definition",
+  "offer_id",
+  "price_agreed",
+  "context"
+]

First observedAug 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare write (readOnlyHint=false), non-idempotent, open-world, non-destructive. Beyond that, the description adds real behavior: the tool refuses unless price_agreed is true, sends an email, notifies Marian, files the inquiry, and warns that optional answers are 'never invented'. It does not address double-send/idempotency risk, which would have earned a 5.

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?

Front-loaded with purpose, the contact-collection scope, and the hard gate before the post-success scripting, so the critical parts come first. It reads as a dense run-on block, and the closing ELC-gift/one-ask sentence is arguably tangential, but nearly every clause carries operational instruction.

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 28-parameter, terminal-step write tool with no output schema, the description covers the gate, the data to pass in, and the expected follow-up (share claim code + booking link). It does not describe the returned payload beyond implying the claim code, nor how failures other than the price gate surface, leaving a small gap.

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?

With 93% schema description coverage the baseline is 3; the description adds genuine meaning by grouping the twelve onboarding answers as pass-through data that must be gathered and 'never invented', and by pinning name/email collection to this step only. It still doesn't clarify the required offer_id/audience/role_band/motivation fields, so it is above baseline but not comprehensive.

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 concrete verb set and outcome: 'emails the visitor a formal itemized offer with a claim code, notifies Marian, and files the inquiry', plus the positioning cue 'the ONLY tool that collects contact details'. That scope claim plus the title ('list prices, no discount') distinguishes it from book_first_session and compose_mentoring_brief without opening a 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 a clear placement rule ('the end of the 10-minute promise', 'Ask for name and email only at this step, never earlier') and a named prerequisite ('the exact price from compose_mentoring_brief'). It stops short of naming explicit alternatives or exclusions beyond the hard gate, so it is clear context without full when-not guidance.

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 tools Inspect

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.

Send the formal itemized offer (list prices, no discount)

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources