Skip to main content
Glama

list_session_slots

Read-only

List open one-off session slots for a mentor's SessionSetup. Requires Authorization: Bearer. setup_id comes from get_sessions_or_services one_off_sessions[].id. Then call book_session with a start.

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": {
      "setup_id": "<setup_id>"
    },
    "name": "list_session_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
setup_idYes
timezoneNoUTC

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
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: it requires an Authorization: Bearer header. It says nothing about pagination, rate limits, or how many slots come back, which is acceptable since an output schema exists.

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 with no filler, front-loaded with the purpose before the prerequisites. Every sentence contributes an actionable fact: what it lists, the auth requirement, and the parameter provenance plus next step.

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, the description need not explain return values, and the booking pipeline is documented end to end. The only real omission is the meaning and effect of the timezone parameter, which matters for a slot-listing tool. Otherwise it is complete for a two-parameter read tool.

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 the parameter burden. It does well for setup_id by giving its provenance (one_off_sessions[].id from get_sessions_or_services), but says nothing about timezone, which controls which day boundaries the returned slots are expressed in. Half the parameters are explained, so it partially compensates for the coverage gap.

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?

The description opens with a specific verb and resource: 'List open one-off session slots for a mentor's SessionSetup.' The phrase 'one-off session slots' implicitly distinguishes it from the intro-call and mentorship-call slot siblings, though it never names an alternative explicitly. An agent knows what it retrieves, even without a direct sibling contrast.

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?

It supplies an explicit workflow chain: setup_id comes from get_sessions_or_services one_off_sessions[].id, and afterwards you call book_session with a start. That names the predecessor, the exact source path for the required parameter, and the successor step. The agent has no ambiguity about when this tool fits in a booking flow.

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