Skip to main content
Glama

list_mentorship_call_slots

Read-only

List open mentorship-call slots for an active mentorship. Requires Authorization: Bearer. mentorship_hash comes from list_mentorships. If the mentor only has an external calendar link, this returns not_available plus that 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": {
      "mentorship_hash": "<mentorship_hash>"
    },
    "name": "list_mentorship_call_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneNoUTC
mentorship_hashYes

Output Schema

NameRequiredDescriptionDefault
nameNo
errorNo
slotsNo
messageNo
setup_idNo
timezoneNo
availableNo
next_stepNo
price_usdNo
booking_urlNo
calendar_linkNo
mentorship_hashNo
application_hashNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds genuinely new behavior: the auth requirement and the fallback path where a mentor with only an external calendar link returns 'not_available' plus that link. This is exactly the kind of non-obvious outcome an agent needs to handle.

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 short sentences, each carrying distinct information (purpose, auth, parameter source, fallback case), with the purpose front-loaded and no filler.

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?

An output schema exists so return values needn't be explained, and the description still covers the important edge case of the external-calendar fallback. Only the timezone parameter interpretation is left unaddressed.

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 description coverage is 0%, so the description must carry parameter meaning. It explains where mentorship_hash originates but ignores the timezone parameter entirely, leaving half the parameters without added semantics beyond the schema's title and default.

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 ('List open mentorship-call slots for an active mentorship'), which is enough to separate it from list_intro_call_slots and list_session_slots by the resource qualifier alone. It stops just short of explicitly naming the alternative tools.

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 a concrete prerequisite ('Requires Authorization: Bearer') and tells the agent where the required parameter comes from ('mentorship_hash comes from list_mentorships'), which is real routing guidance. It does not state when to prefer this over the intro-call or session-slot siblings.

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