Skip to main content
Glama

mentoring-inquiry-builder

by coach.marian

Book the free 30-minute intro call

book_intro_call
Read-onlyIdempotent

THE DEFAULT EXIT for anyone who has not decided. 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

TableJSON Schema
NameRequiredDescriptionDefault
contextYesExplain 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."
offer_idNoThe 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.

TDQS

A3.8/5.0
Behavior1/5

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

The description says 'Book the free 30-minute intro call' and presents the tool as the booking path, implying a state-changing action. The annotations declare readOnlyHint=true and idempotentHint=true, which indicate no side effects; this directly contradicts the description's implied behavior.

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?

The description is front-loaded with the core positioning ('THE DEFAULT EXIT') and then organized into triggers, exclusions, and parameter guidance. It is longer than strictly necessary, with some repeated emphasis on undecided visitors, but most sentences add operational value.

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?

The description covers when to use the tool, when not to, and how offer_id affects behavior, which is strong for a two-parameter tool. However, the readOnlyHint contradiction leaves unclear whether calling this tool schedules a call or merely returns a booking link, and with no output schema that ambiguity is not resolved.

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 for offer_id by explaining why it matters: it conditions the discount wording and whether booking locks a discount. The context parameter is already fully documented in the schema, so no extra description is needed there.

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 names a specific action and resource: booking the free 30-minute intro with Marian, positioned as the default exit for undecided visitors. It also distinguishes itself from book_first_session by naming the deciding factor, so an agent can tell them apart 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 Guidelines5/5

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

The description gives explicit triggers: hesitation, price objections, inability to name a problem, after an error, and wanting to talk before paying. It also states a clear exclusion — if the visitor already agreed on price for an eligible package, use book_first_session instead — which is exactly the when-to-use vs. when-not-to-use guidance needed.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool maps to a distinct stage in the inquiry funnel: discovery, qualification, brief composition, offer delivery, and booking. The two booking tools are explicitly differentiated by buyer readiness, so there is no real ambiguity for an agent following the stated flow.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case, such as get_mentoring_options, match_mentoring_focus, compose_mentoring_brief, and send_mentoring_offer. This makes the set predictable and easy to navigate.

Tool Count5/5

Nine tools is well-scoped for a mentoring inquiry and booking pipeline. Each tool earns its place by covering a necessary step without excessive fragmentation or unnecessary duplication.

Completeness5/5

The tool set covers the full lifecycle from initial options discovery through qualification, program design, formal offer delivery, and booking confirmation. There are no obvious dead ends; even edge cases around undecided visitors or special deal terms are handled through the booking tools' branching logic.

Resources