Skip to main content
Glama

list_intro_call_slots

Read-only

List open intro-call slots for an accepted application. Requires Authorization: Bearer. Available only when the mentor accepted and the intro call is not yet scheduled. Pick a start and call book_intro_call.

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": {
      "application_hash": "<application_hash>"
    },
    "name": "list_intro_call_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneNoUTC
application_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

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond annotations: Bearer authorization is required, and access is gated on mentor acceptance and an unscheduled intro call. It does not mention pagination, rate limits, or other open-world behaviors, but it adds meaningful operational context.

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?

The description is three short sentences with no wasted wording. Availability and next-step guidance are front-loaded and immediately actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a relatively simple read-only listing operation and has an output schema, so return values need not be explained. However, the description is incomplete for its parameters: with 0% schema coverage, the lack of explanation for application_hash and timezone is a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description needs to compensate for undocumented parameters. It partially contextualizes application_hash by tying the application to an accepted application, but it does not explain the hash format, and it does not mention the timezone parameter or default UTC at all.

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 states a specific verb and resource: 'List open intro-call slots for an accepted application,' and adds the key gating condition that the mentor accepted and the call is not scheduled. It names book_intro_call as the follow-up, but does not explicitly distinguish this listing tool from other slot-listing siblings such as list_mentorship_call_slots.

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?

It clearly states when the tool is available ('only when the mentor accepted and the intro call is not yet scheduled') and what to do next ('Pick a start and call book_intro_call'). The alternatives are only partially addressed because it does not say what to use if those preconditions are not met.

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