Skip to main content
Glama

get_mentor_profile

Read-only

Fetch the full public profile for a single MentorCruise mentor. Use the username from a search_mentors result. Returns name, headline, company, bio, skills, languages, rating, monthly price, response time, open spots, and the public profile URL. Returns {'error': 'not_found'} if the mentor doesn't exist or is hidden.

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>"
    },
    "name": "get_mentor_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYes

Output Schema

NameRequiredDescriptionDefault
bioNoPlain-text biography (HTML stripped).
nameNoFull name.
tagsNoFree-form tags.
errorNoError code: 'not_found' or 'rate_limit_exceeded'. Absent on success.
toolsNoTools/technologies.
ratingNoAverage review rating (0-5), or null if unrated.
skillsNoSkill tags.
companyNoCurrent company.
messageNoHuman-readable error detail.
headlineNoOne-line self-description.
locationNoDisplay location.
usernameNoMentor slug.
job_titleNoCurrent role.
languagesNoLanguages spoken.
does_callsNoWhether the mentor offers video calls.
industriesNoIndustry tags.
open_spotsNoMentee slots currently open.
top_mentorNoTop Mentor status.
profile_urlNoAbsolute URL to the public profile.
review_countNoNumber of reviews.
lowest_price_usdNoCheapest offering in USD (subscription or one-off).
open_to_inquiriesNoWhether the mentor accepts free inquiries.
profile_image_urlNoAbsolute URL to the profile image.
response_time_hoursNoMedian response time in hours; may be fractional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint=true, destructiveHint=false and openWorldHint=true; the description adds genuinely new behavior by specifying the payload fields returned and the exact failure shape ({'error': 'not_found'}) for missing or hidden mentors. That error contract is the kind of detail annotations cannot convey, though rate limits or caching behavior are unmentioned.

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?

Three tight sentences with the action front-loaded, then the parameter sourcing, then the return contract and error case. No filler or repetition; every sentence adds information.

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 one-parameter read tool with an output schema and full annotation coverage, the description covers purpose, parameter origin, and the error path adequately. The enumerated return fields duplicate what the output schema already provides, which is slightly redundant rather than harmful.

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 description coverage is 0% for the single parameter, so the description must carry the meaning, and it does: `username` is identified as an identifier taken from a search_mentors result rather than an arbitrary string. It could still note case sensitivity or format expectations, so not a 5.

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?

Specific verb ("Fetch") plus precise resource ("the full public profile for a single MentorCruise mentor"), and it explicitly positions itself as the follow-up to search_mentors, so an agent can separate it from the search sibling 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 Guidelines4/5

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

Gives clear operational context: it tells the agent to supply the `username` from a search_mentors result, which effectively defines the intended workflow (search first, then fetch). It stops short of explicit exclusions such as what to do for bulk lookups or whether other profile sources exist.

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