Skip to main content
Glama

Change a pack

update_pack

Changes a pack on sale. Only the fields you send change. Packs members have already bought keep their own terms and are not affected. Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>",
      "pack_id": "<pack_id>"
    },
    "name": "update_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName shown to members, e.g. "Move 10".
addressYesThe venue’s address name, the "name" in name.bookare.app.
classesNoHow many classes the pack holds (1-200). Leave out when unlimited is true.
pack_idYes
taglineNoOne short line under the name.
price_eurNoPrice in euro, e.g. 59.9.
unlimitedNoTrue for unlimited classes until it expires.
access_keyYesThe venue’s access key.
valid_daysNoDays the pack is valid from the day it is bought (1-730).
descriptionNoLonger description shown with the pack.
off_peak_onlyNoTrue if it can be used only for classes marked off-peak.
on_sale_untilNoYYYY-MM-DD: a limited-time pack members can buy until the end of that day. Empty string = always on sale.
class_type_idsNoClass types the pack can be used for. Empty list = all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a non-read-only, non-destructive, non-idempotent mutation, so the bar is lower. The description adds genuinely useful behavior the annotations don't: partial-update semantics and the fact that already-purchased pack instances retain their own terms. It omits permissions/error behavior and what the response contains, and "only the fields you send change" sits slightly uneasily with idempotentHint=false since setting a field twice is idempotent.

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 operation, then the patch rule, then the side effect. No filler wording; only slight waste in restating the venue/key scoping that the schema already documents.

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 13-parameter mutation tool with no output schema, the description covers the essentials an agent needs before calling: patch semantics, tenant scoping, and the effect on existing purchased packs. It could go further on permissions or failure modes, but nothing critical 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 description coverage is 92%, so the schema already explains nearly every field including formats, ranges, and the empty-string/empty-list conventions. The description adds only the general "only the fields you send change" rule and the address/access-key scoping, giving no field-level detail beyond the schema; 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?

"Changes a pack on sale" names a specific verb and resource and is clearly distinct from create_pack/delete_pack/set_pack_visibility by the sibling list. The qualifier "on sale" slightly narrows the scope ambiguously (is it about the sale flag, or about packs that are listed for sale?), but an agent can still identify the operation.

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 description establishes the patch contract ("Only the fields you send change"), which implicitly tells the agent to send this tool for partial edits rather than recreating. It gives no explicit comparison to create_pack or set_pack_visibility, and names no preconditions beyond needing address and access key.

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