Skip to main content
Glama

NextUp Walk-in

Link to buy a package or membership

purchase_link
Read-onlyIdempotent

The packages and memberships a place sells online, and the link where the person pays for them. Only for places whose owner turned it on. You cannot pay for them: they open the link and pay on the place's own secure Stripe page. Gift cards aren't sold online.

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": "purchase_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe place's slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish a safe, read-only, closed-world, idempotent lookup, so the bar is lower. The description still adds genuine context: the agent cannot complete payment, the payer is sent to the place's own Stripe page, and the owner must have opted in — all behavior an agent could otherwise get wrong. It stops short of saying what is returned when the feature is disabled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the resource and then the key constraints, with no filler. The colon construction in 'You cannot pay for them: they open the link' is slightly compressed but still readable and earns its place.

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 one-parameter read tool with no output schema, the description covers the resource, the opt-in precondition, the gift-card exclusion, and the external payment flow. The remaining gap — what is returned when the owner hasn't enabled it and the shape of the response — is minor but real.

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?

There is a single required 'slug' parameter documented at 100% schema coverage, so the schema carries the burden. The description adds no format, source, or lookup hints for 'slug' beyond what the schema already says, which makes the baseline score appropriate.

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 identifies the concrete resource — packages and memberships a place sells online, plus the payment link — and rules out gift cards. It never states an explicit verb (retrieve/return) and doesn't name how it differs from sibling tools like booking_link or join_link, leaving the agent to infer the resource split.

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 gives one real precondition ('Only for places whose owner turned it on') and clarifies these are not gift cards. However, there is no guidance on when to choose this over booking_link or join_link, and implied usage must be inferred from the resource name alone.

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