Skip to main content
Glama

NextUp Walk-in

Link to join the line

join_link
Read-onlyIdempotent

A link the person taps to join the place's line from their phone, optionally with a service and team member filled in. You cannot join for them: they 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>"
    },
    "name": "join_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe place's slug
memberIdNoOptional team member id from get_place
serviceIdNoOptional 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 declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuinely useful behavior beyond them: the tool produces a link, the request is not completed on the person's behalf, and confirmation happens on the place's own page — an important constraint for an agent trying to 'complete' a join.

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, both load-bearing, with the core purpose front-loaded and the hand-off constraint immediately after. Nothing is redundant or padded.

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 simple three-parameter, read-only link generator with no output schema, the description covers what the tool produces and the key limitation on the agent's role. It stops short of explaining how the returned link should be presented or how long it remains valid, which is a minor 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% and each parameter already carries its own description and sourcing hint. The description only restates that service and team member are optional, adding no format or interaction detail beyond the schema, so the 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 states a specific verb and resource: a link the person taps to join the place's line, with optional service and member pre-filled. That is clearly distinguishable from a generic link tool, though it does not explicitly contrast itself with siblings like booking_link or purchase_link.

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?

It conveys the operating context ('You cannot join for them: they confirm on the place's own page'), which tells the agent this is a hand-off rather than a direct action. However, it never states when to choose this over booking_link or purchase_link, so alternative selection is left to inference.

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