Skip to main content
Glama

Find free slots

find_slots
Read-only

Check available start times for a service on a given date before offering a booking time. Use it to confirm staff availability and avoid scheduling conflicts.

Instructions

Free start times for a service on a date. Always check before offering a time.

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": {
      "service": "<service>",
      "date": "<date>"
    },
    "name": "find_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate as YYYY-MM-DD
staffNoOptional staff id
serviceYesService id from list_services

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a non-mutating lookup, so the description's remaining burden is to explain the shape and caveats of the result. It does not say whether returned times respect service duration, timezone, or existing bookings, nor how many slots come back — meaningful gaps for a availability check. The pre-booking instruction adds modest workflow value beyond annotations.

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 short, front-loaded sentences with no filler — the resource is stated first, then the action directive. It is arguably slightly too terse for an availability tool, but nothing is wasted.

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?

There is no output schema, so the description should at least characterize what a caller receives (a list of start times, ordering, format/timezone); it only implies this via "free start times." Combined with 100% schema coverage on inputs, it is adequate but leaves a real gap on the return side.

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 100%, so service, date, and staff are already documented in the schema (including "Service id from list_services"). The description only restates the service/date scope and adds nothing about how the optional staff parameter narrows results, so baseline 3 applies.

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?

Names a specific resource (free start times) scoped by two qualifiers (service, date), which is enough for an agent to distinguish it from find_bookings (existing bookings) by implication. It stops short of naming a sibling or stating the contrast explicitly, so it is clear but not fully differentiated.

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?

"Always check before offering a time" is an explicit precondition that ties invocation to the booking workflow, telling the agent to call this before proposing a slot. It gives no exclusions or alternatives (e.g., when to prefer find_bookings or a staff-filtered search), so context is clear but incomplete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.