Skip to main content
Glama

Free meeting times

find_meeting_slots
Read-onlyIdempotent

Free times in a mentor's published hours that the person (a mentee) can book, after the mentor's and the person's own calendars, blocked times and the programme's minimum notice. Each free time has the start that books it. As mentor, with mentor_id empty: the person's own free published times, also free in the calendar of the mentee (or group) in with_member_id.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days to look at (default 14).
fromNoFirst day to look at, YYYY-MM-DD (default today).
programYesId or domain of one of the person's programmes.
mentor_idNoThe mentor's id (as mentee).
with_member_idNoAs mentor: the mentee or group whose calendar is also checked (optional).

Output Schema

NameRequiredDescriptionDefault
fromNoFirst day, YYYY-MM-DD.
noteNoWhy there are few or no slots.
slotsNoFree starts to book, with their length.
untilNoLast day, YYYY-MM-DD.
programNoProgramme domain.
time_zoneNoThe programme's time zone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: slots are already filtered by both calendars, blocked times and the programme's minimum notice, and each slot carries a `start` value that is what gets booked. It does not discuss result volume, pagination, or what happens when no slots are free.

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?

Two sentences, front-loaded with the core definition of what a free time is, then the mode split. Dense but every clause carries information. The repeated 'the person' phrasing and the nested parenthetical slow comprehension slightly.

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-value detail is not required, and the description covers the non-obvious parts: the filtering inputs, the meaning of an empty mentor_id, and the role of with_member_id. For a five-parameter read tool this is close to complete, with only edge-case behavior left unstated.

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%, so every parameter is documented in the schema, which sets the baseline at 3. The description does add meaning the schema lacks: that an empty mentor_id flips the tool into the mentor's own-perspective mode and that with_member_id is only relevant in that mode. That clarification is genuinely useful but limited to two of five parameters.

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 names a specific resource and verb: free/bookable meeting slots derived from a mentor's published hours, filtered by both parties' calendars, blocked times and programme notice. It distinguishes the two operating modes (mentee with mentor_id set, mentor with mentor_id empty). It stops short of naming the nearest sibling, list_my_availability, so the boundary against that tool must be inferred.

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 gives concrete when-to-use context by describing both invocation modes: pass a mentor_id to see a mentor's bookable slots, or leave it empty as a mentor to see one's own published times that are also free for with_member_id. It does not state exclusions or point to alternative tools for related needs such as listing raw availability.

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