Skip to main content
Glama

Gaplessly Booking

by com.gaplessly
OverviewDiscussionsAdmin

Find appointment times

find_appointment_times
Read-onlyIdempotent

Free appointment times at one venue for one service, over up to two weeks. For salons, clinics, studios and anywhere a guest books a named service with a provider. Use find_table_times for a restaurant instead.

Needs a service id from get_venue. Each returned time has an at label to show the guest and a slotToken. The token is the booking handle: it is signed, it expires in about 30 minutes, and it is the only way a time can be booked later. Pass it back exactly as given, never edited, and never reuse one from a different venue. An empty times array for a day means that day is genuinely unavailable, not that something failed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoHow many consecutive days to search from that day, 1 to 14. Defaults to 3.
fromNoWhich day to start from: the word "today", the word "tomorrow", or an exact calendar date as YYYY-MM-DD. Resolved against the venue's own current date, which is often not yours. Do not send a phrase like "next Tuesday" or a time of day; both are rejected.
venueYesThe venue's booking slug, exactly as get_venue returned it or as it appears in the venue's own booking link: the last path segment of gaplessly.com/book/<slug>, or the first label of <slug>.gaplessly.com. Not the business name.
serviceIdYesOne service id from this venue's get_venue result. Not a service name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"How many consecutive days to search from that day, 1 to 14. Defaults to 7."New value: +"How many consecutive days to search from that day, 1 to 14. Defaults to 3."
    • changedInput schema / properties / venue / description
      Previous value: -"The venue's booking slug, exactly as get_venue returned it or as it appears in the venue's own booking link (the last path segment of gaplessly.com/book/<slug>). Not the business name."New value: +"The venue's booking slug, exactly as get_venue returned it or as it appears in the venue's own booking link: the last path segment of gaplessly.com/book/<slug>, or the first label of <slug>.gaplessly.com. Not the business name."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish read-only/idempotent safety, and the description adds substantial context beyond them: the `slotToken` is signed, expires in ~30 minutes, is the only way to book later, must not be edited or reused across venues, and an empty `times` array means genuinely unavailable rather than failed. This is exactly the non-obvious behavior an agent needs.

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 tight paragraphs, front-loaded with what the tool does and the sibling exclusion, then prerequisites, then the critical token contract. No sentence is filler.

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

Completeness5/5

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

With no output schema, the description compensates by explaining the returned time shape (`at` label, `slotToken`), the token's lifecycle, and the meaning of an empty result. Nothing needed to call or interpret this tool is missing.

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 the schema already documents every parameter in detail (including the venue slug formats and the accepted `from` values). The description only reinforces that serviceId must come from get_venue, adding little beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and resource with scope ('Free appointment times at one venue for one service, over up to two weeks'), and it explicitly names the sibling it is not (find_table_times) plus the verticals it serves. An agent can distinguish it from find_table_times without opening either schema.

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 names the alternative and the condition that selects it ('Use find_table_times for a restaurant instead') and states the prerequisite ('Needs a service id from get_venue'). Both when-to-use and what's-needed-before are explicit.

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

All Gaplessly Booking toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources