Skip to main content
Glama

NextUp Walk-in

Open booking times

available_times
Read-onlyIdempotent

Open start times (up to 12) on one date for one service, when the place takes online bookings. Times are in the place's own time zone. Pass memberId (from get_place) to see only that team member's times. Use it when the person wants an appointment and asks when; then give them booking_link. For walking in now, use join_link instead. If the place doesn't take online bookings, the service isn't offered, or the day is full, it says so (try another date).

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": {
      "slug": "<slug>",
      "serviceId": "<serviceId>",
      "date": "<date>"
    },
    "name": "available_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate as YYYY-MM-DD, in the place's time zone
slugYesThe place's slug
memberIdNoOptional team member id from get_place
serviceIdYesA service id from get_services

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (readOnly/idempotent/non-destructive/closed-world), the description discloses the 12-result cap, that times are in the place's own time zone, and that the tool reports a reason rather than failing silently when bookings aren't offered, the service is missing, or the day is full. It does not describe the shape of a returned time entry, but the annotations already carry the safety profile so the disclosure burden is lighter.

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?

Front-loads what the tool returns and its scope, then layers time zone, the optional filter, usage routing, and failure modes. Every sentence contributes a distinct fact; the parentheticals are compact rather than padding.

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?

For a read-only lookup with a fully documented four-parameter schema and no output schema, the definition covers scope, units/time zone, optional filtering, the next tool to call, the competing tool to avoid, and the error cases. Nothing an agent needs to select or invoke it correctly 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, and the description largely restates them (memberId 'from get_place', one date, one service). The one genuine addition is the filtering effect of memberId ('see only that team member's times'), which the schema does not spell out, so it sits slightly at the baseline rather than above it.

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?

States a specific verb and resource ('Open start times') with tight scope qualifiers: up to 12 results, one date, one service, and only where the place takes online bookings. It is immediately distinguishable from join_link (walk-ins) and booking_link (the follow-up action) without opening any 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?

Gives an explicit trigger ('when the person wants an appointment and asks when'), an explicit exclusion with the alternative named ('For walking in now, use join_link instead'), and the downstream step ('then give them booking_link'). It also names the three conditions under which the tool should not be expected to return times.

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