Skip to main content
Glama
Sign In

Mentornity

by com.mentornity
OverviewDiscussionsAdmin

Member profile

get_member_profile
Read-onlyIdempotent

The profile of a mentor, a mentee or a mentee group (team, startup, venture) in a programme, as the person may see it in the web app: headline, about, and the answers to the programme's profile questions; for a group also its members, website and LinkedIn, which are what to look the venture up by on the web.

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

Input Schema

NameRequiredDescriptionDefault
roleNoWhich side the member is on (default mentor).
programYesId or domain of one of the person's programmes.
member_idYesThe member's (or group's) id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description adds real value by disclosing the shape of what is returned and the caveat 'as the person may see it', hinting at viewer-dependent visibility, but it says nothing about behavior on an unknown member_id, unknown program, or whether fields can be empty or hidden.

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?

One dense, front-loaded sentence that begins with the resource and then lists contents; nothing is padded. The trailing clause 'which are what to look the venture up by on the web' is slightly awkward and could be trimmed without loss.

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 read-only, three-parameter lookup with full schema coverage and no output schema, the description does the main remaining job of sketching the return payload, including the extra group fields. Missing only edge-case behavior (not found, restricted visibility) to be fully complete.

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% and the schema already documents role (with default), program (id or domain) and member_id (24-hex id). The description adds only marginal meaning, effectively clarifying that role=group changes the returned content by adding members, website and LinkedIn; the rest duplicates the schema.

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+resource: retrieves the profile of a mentor, mentee or mentee group within a programme, and enumerates the visible fields (headline, about, profile answers, plus members/website/LinkedIn for groups). It reads as 'someone else's profile in a programme', which implicitly contrasts with the sibling get_my_profile, but never names that sibling to make the distinction explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the scope phrase 'in a programme' and by the role enum, but there is no explicit when-to-use / when-not-to-use guidance, no statement that get_my_profile should be used for the caller's own profile, and no prerequisites (e.g. membership in the programme) are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mentornity toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources