Skip to main content
Glama

NextUp Walk-in

Link to book a time

booking_link
Read-onlyIdempotent

A link the person taps to book an appointment, with the service (and optionally a team member and date) filled in. You cannot book for them: they pick a time and confirm on the place's own page.

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

Input Schema

NameRequiredDescriptionDefault
dateNoOptional date as YYYY-MM-DD
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

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, openWorldHint=false), so the description earns credit for adding behavior they don't: that this tool only produces a link and that booking authority stays with the end user on the place's own page. It does not say whether links expire or are reusable, which would be the remaining useful detail for an idempotent link generator.

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?

Two sentences with no filler: the first defines the output and its pre-filled fields, the second front-loads the critical constraint about who completes the booking. Nothing could be removed without losing signal.

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?

For a four-parameter read-only link builder with full schema coverage and no output schema, the definition covers what the tool yields and who acts on it. A brief note on the returned value's form (a URL string) or link lifetime would close the last gap.

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's mapping of service as core with team member and date as optional matches the schema's required/optional split. It adds no syntax, format, or sourcing detail beyond what the schema fields say, 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?

The description names a concrete artifact — a booking link the person taps — with the service pre-filled and optionally a team member and date. That is more specific than the title alone and an agent can tell it apart from join_link or purchase_link by the resource it produces. It stops short of an explicit verb like 'generate a deep link', so it is clear but not maximally sharp.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence conveys an important usage constraint — the agent cannot complete the booking on the person's behalf, they confirm on the place's own page — which implies this tool is the hand-off step. However, it never states when to reach for this versus available_times (to surface slots) or find_walk_in_places, and no preconditions (e.g., id values must come from get_place/get_services) are stated in prose.

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