LobbyStack

Check open times

check_availability

Read-onlyIdempotent

Lists open start times for one service, in 30-minute steps within opening hours, checked against staff calendars and existing bookings. Dates are YYYY-MM-DD in the business time zone; the range can span up to 7 days. Returned times are UTC. Pass a starts_at value unchanged to book_appointment or reschedule_appointment.

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_id": "<service_id>",
      "start_date": "<start_date>"
    },
    "name": "check_availability"
  }
}

Input Schema

Name	Required	Description
`end_date`	No	Last day, YYYY-MM-DD. Defaults to start_date. At most 7 days after start_date, counting both.
`staff_id`	No	Only times when this staff member is free, from list_staff.
`service_id`	Yes	The service to book, from list_services.
`start_date`	Yes	First day, YYYY-MM-DD, in the business time zone.

Output Schema

Name	Required	Description
`data`	Yes
`has_more`	Yes
`next_cursor`	Yes	Pass as cursor to get the next page. Null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description focuses on what they cannot say: 30-minute granularity, availability derived from staff calendars plus existing bookings, and the non-obvious timezone split (input dates in business time zone, returned times in UTC). The round-trip contract that returned starts_at values can be passed unchanged to the booking tools is behavior an agent would otherwise get wrong.

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 sentences, each carrying distinct information: what is returned, the date/timezone conventions, and the handoff contract. No filler and the most decision-relevant detail (what the times represent) leads.

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 an output schema present, the description does not need to enumerate return fields, and it correctly spends its space on timezone handling, granularity, and the booking handoff. Nothing an agent needs in order to call this correctly and use the result 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 coverage is 100%, so all four parameters are already documented with formats, defaults, and the 7-day range constraint. The description restates the date format and range limit but adds no syntax or meaning beyond the schema, so the baseline of 3 applies.

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 first sentence names a specific verb (Lists) and resource (open start times) and pins down scope: one service, 30-minute steps, within opening hours, checked against staff calendars and existing bookings. That distinguishes it clearly from list_appointments and list_staff without needing the schema.

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 states the downstream path explicitly — pass a starts_at value unchanged to book_appointment or reschedule_appointment — which tells an agent exactly where this tool sits in the workflow. It stops short of naming when not to use it (e.g., use list_appointments for already-booked slots), so it is clear context rather than full routing guidance.

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

All LobbyStack tools Inspect

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

Need Help?