Skip to main content
Glama

Find mentors

search_mentors
Read-onlyIdempotent

Searches the mentors the person may see in a programme (in a programme where mentees choose, only those they may request), for example by a skill ("sales"); with free_on, only those with bookable free times then. Returns each mentor's member id.

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": {
      "program": "<program>"
    },
    "name": "search_mentors"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWith free_on: how many days (default 1).
pageNoPage, from 1 (20 per page).
queryNoWords to search in names and profiles (optional).
free_onNoOnly mentors with free times you can book from this day, YYYY-MM-DD (optional; checks the first 10 found).
programYesId or domain of one of the person's programmes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description still adds real value: it discloses that only member ids come back and that the free_on check is limited to the first 10 found, a material sampling caveat not present in the schema or annotations.

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?

A single dense sentence with the resource and permission scope front-loaded, followed by the optional filters. Parenthetical asides earn their place, though the nested clauses make it slower to parse than necessary.

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?

There is no output schema, and the description correctly states the return shape (member ids). With all five parameters documented in the schema, the remaining gap is minor: nothing about result volume or ordering, though the '20 per page' note in the schema covers pagination.

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 the baseline is 3. The description does add cross-parameter meaning that the per-field schema cannot convey, notably that days only takes effect with free_on, but it adds nothing on query or program beyond the schema wording.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Searches the mentors") plus the permission scope ("the mentors the person may see in a programme") and the return value ("each mentor's member id"). It implicitly distinguishes itself from search_mentees by naming mentors, but never names an alternative explicitly.

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?

Explains the conditional mode clearly: with free_on only mentors with bookable free times are returned, and days only applies alongside free_on. It also flags the mentee-choice programme case where only requestable mentors are returned, but gives no explicit when-not guidance or named alternative tool.

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