Skip to main content
Glama

AI mentoring fit and book: check the fit with Marian Kamenistak and book the first session in 10 minutes

get_mentoring_options
Read-onlyIdempotent

START HERE for anyone considering 1:1 engineering-leadership mentoring with Marian (marian.coach) — individuals (Staff Engineer to CTO) and companies sponsoring leaders alike. Returns a short briefing: the tool pitch, the time promise (a formal offer in under 10 minutes), every package with real prices (same as the website, no discount through any door), and the qualifying questions with valid answer ids. Depth on request via the optional topic argument (engagement, objections, pricing, why_marian, visibility, focus_areas, onboarding, b2b, terms, endings). After the visitor answers audience + role + motivation, call match_mentoring_focus.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_mentoring_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOptional depth, one of: engagement, objections, pricing, why_marian, visibility, focus_areas, onboarding, b2b, terms, endings. Omit it for the opening briefing (questions and packages).
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / topic
      Added value: +{
      +  "description": "Optional depth, one of: engagement, objections, pricing, why_marian, visibility, focus_areas, onboarding, b2b, terms, endings. Omit it for the opening briefing (questions and packages).",
      +  "type": "string"
      +}
  2. Changed2 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."
    • removedInput schema / required
      Removed value: -[
      -  "context"
      -]
  3. 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"
      +]
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot: what the response contains (pitch, packages, prices, qualifying questions with valid answer ids) and the guarantee that pricing is identical to the website with no discount through any door. It does not discuss limits on repeated calls or how the briefing is structured, which is a minor gap given the promotional framing consumes some of the text.

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 'START HERE' and organized as purpose, return contents, then optional depth, which is easy to scan. It loses a point for density and repetition: the ten topic values are re-listed in a parenthetical that duplicates the enum, and marketing lines like 'no discount through any door' add tone rather than selectable information.

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?

For a zero-required-parameter, read-only briefing tool with no output schema, the description carries the return-content burden fully and even names the follow-up tool and trigger. Nothing an agent needs in order to call it correctly or interpret the result is missing.

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 100%, so both parameters are already documented, including the exact topic list and the 'omit it for the opening briefing' instruction; the description largely restates that enumeration. It does add the useful framing that the topics are 'depth on request' and that the briefing is the default, but this is marginal value over the schema rather than new syntax or format detail.

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: it returns a short briefing containing the pitch, the time promise, every package with real prices, and the qualifying questions with valid answer ids. The scope (1:1 engineering-leadership mentoring with Marian, for individuals Staff Engineer to CTO and sponsoring companies) is precise enough that an agent can separate it from match_mentoring_focus and the booking tools 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 Guidelines5/5

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

Explicit entry point ('START HERE for anyone considering...') plus an explicit sequencing rule: after the visitor answers audience + role + motivation, call match_mentoring_focus. It also names the condition for depth (optional topic argument) versus the default opening briefing, so both when-to-use and when-not-to-use are covered.

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