Skip to main content
Glama

apply_to_mentor

Send a mentorship application to a mentor on the signed-in mentee's behalf. Requires Authorization: Bearer and a verified email. goal must be a real, specific message (min 50 characters). Optional plan_hash selects a pricing plan from get_sessions_or_services. The mentor is notified after a spam check. This does not charge yet; when they accept, call pay_application.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>",
      "goal": "<goal>"
    },
    "name": "apply_to_mentor"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes
timelineNo
timezoneNoUTC
usernameYes
last_nameNo
plan_hashNo
user_infoNo
first_nameNo
introductionNo
mentee_questionNo
time_expectationsNo
service_expectationsNo

Output Schema

NameRequiredDescriptionDefault
hashNoPass to pay_application.
errorNo
statusNodraft, new, pending, accepted, rejected, withdrawn.
unreadNoTrue when the mentee has an unread Pinax message.
messageNo
pay_urlNoREST URL that accepts an MPP credential if credits are short.
payableNoTrue when the mentor accepted and payment is due.
messagesNo
next_stepNo
plan_hashNo
price_usdNo
created_atNo
credits_usdNo
mentor_nameNo
status_noteNo
can_withdrawNoTrue when withdraw_application will succeed.
dashboard_urlNo
action_requiredNoreply_to_mentor, waiting_on_mentor, book_intro_call, or start_mentorship.
mentor_usernameNo
sent_message_idNo
intro_call_scheduledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: auth requirements, a verified-email gate, a spam check before the mentor is notified, and the fact that no charge occurs at this step. The annotations already declare openWorldHint=true and destructiveHint=false, so the remaining gap is minor (no detail on failure modes or what the spam check rejects).

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

Conciseness5/5

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

Four tight sentences, front-loaded with the action and identity, then prerequisites, then the plan_hash dependency, then the no-charge/next-step rule. No filler.

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?

An output schema exists, so return values need not be described, and the auth and follow-up flow are well covered. However, for a 12-parameter tool with zero schema coverage, leaving ten parameters unexplained is a real completeness gap for an agent trying to fill the form correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 12 parameters, so the description must carry the load, but it only explains goal (min 50 characters, must be a real specific message) and plan_hash (selects a pricing plan from get_sessions_or_services). Ten parameters, including timeline, timezone, introduction, mentee_question, and the name fields, get no meaning at all.

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 ('Send a mentorship application to a mentor') plus the acting identity ('on the signed-in mentee's behalf'). It also implicitly separates itself from pay_application and get_sessions_or_services by naming them in later sentences.

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 explicit preconditions (Authorization: Bearer, verified email) and an explicit sequencing rule: this does not charge yet, and pay_application is the follow-up once the mentor accepts. It also points to get_sessions_or_services as the source of plan_hash, so the agent knows where to get that value.

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