Skip to main content
Glama

get_sessions_or_services

Read-only

List the mentorship plans (ongoing subscriptions) and one-off sessions a mentor offers. Use this after get_mentor_profile when the user is comparing what they'd get for the money.

TWO DIFFERENT BOOKING ROUTES — pay attention to booking_route on each item:

  • subscriptions[] (ongoing mentorship): book via the apply flow. Each subscription item already includes its booking_url. You can also pass its hash to create_booking_link(plan_hash=...).

  • one_off_sessions[]: book directly on the session page. Each item includes its booking_url — share THAT URL with the user, do NOT route a one-off session through create_booking_link.

Top-level requires_intro_call flags whether this mentor offers an intro call before signup (free or paid). When true, all subscription booking_urls route the user to the scheduler first. Read intro_call_note for whether it is free or paid, and mention that to the user when you share the link.

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_sessions_or_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYes

Output Schema

NameRequiredDescriptionDefault
errorNoError code: 'not_found' or 'rate_limit_exceeded'. Absent on success.
messageNoHuman-readable error detail.
usernameNoMentor slug.
subscriptionsNoOngoing mentorship plans, cheapest first.
intro_call_noteNoGuidance about the intro call (free or paid); null when the mentor offers none.
one_off_sessionsNoOne-off bookable sessions.
requires_intro_callNoWhen true, every subscription booking_url routes to the scheduler first; mention the intro call (see intro_call_note for free vs paid).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds behavior the annotations cannot: each item carries a booking_route, subscription items expose a hash usable with create_booking_link, and requires_intro_call changes where every subscription booking_url sends the user. It does not mention pagination, result size limits, or what happens if a mentor offers nothing, so it stops short of a 5.

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?

Front-loaded with the purpose, then cleanly sectioned under a routing header with two bullets, and closing on the intro-call flag. Every block carries operational information, though the routing explanation is dense and could be tightened 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?

With an output schema present, return-field shapes need not be explained, and the description instead covers the decision logic an agent needs: which route each item takes and how requires_intro_call/intro_call_note alter the message to the user. Missing only edge-case handling, such as a mentor with no subscriptions or sessions, which is a minor gap for a read-only lookup.

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?

The single parameter is `username` with 0% schema description coverage, and the description never states that it identifies the mentor whose offerings are listed — it only implies a mentor context. The meaning is inferable from the sibling get_mentor_profile, but the description does not compensate for the schema gap.

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?

Opens with a specific verb and two named resources: 'List the mentorship plans (ongoing subscriptions) and one-off sessions a mentor offers.' The parenthetical disambiguates 'plans' from generic plan listings, and the split into subscriptions[] vs one_off_sessions[] tells an agent exactly what comes back, distinguishing it from get_mentor_profile and create_booking_link.

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?

Explicitly sequences the tool: 'Use this after get_mentor_profile when the user is comparing what they'd get for the money.' It then names a sibling and the condition for not using it — 'do NOT route a one-off session through create_booking_link' — which is a rare, high-value negative instruction with a concrete alternative (share the booking_url).

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