Skip to main content
Glama

Create a pack

create_pack

Adds a new pack to what the venue sells. It is visible to members straight away. Returns the new pack. 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>",
      "name": "<name>",
      "valid_days": "<valid_days>",
      "price_eur": "<price_eur>"
    },
    "name": "create_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName 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.
taglineNoOne short line under the name.
price_eurYesPrice in euro, e.g. 59.9.
unlimitedNoTrue for unlimited classes until it expires.
access_keyYesThe venue’s access key.
valid_daysYesDays 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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, but the description adds genuinely new behavior: the pack is "visible to members straight away" (immediate public effect) and the call "Returns the new pack" (return value, and no output schema exists to convey it). It omits the duplicate-creation risk implied by idempotentHint=false and any permission/failure behavior, keeping it below 5.

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?

Three short sentences, zero filler, with the creation action and immediate member visibility front-loaded and the venue-scoping constraint at the end. Nothing is repeated from the title and every sentence carries information.

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 12-parameter mutation tool with full schema coverage, no output schema, and annotations covering the safety profile, the description supplies the missing return-value statement and the visibility consequence. The remaining gap is error/precondition behavior and duplicate handling, which is minor given how much the structured fields already carry.

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 100%, so all 12 parameters, including the required address/access_key pairing and the valid_days/price_eur units, are already documented in the schema. The description only echoes that address and access key identify the venue, adding essentially no semantics beyond structured data — baseline 3 is correct.

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?

States a specific verb and resource ("Adds a new pack") plus the scope ("what the venue sells"), which is enough to distinguish it from update_pack/delete_pack by name alone. It stops short of explicitly naming the sibling it is not, so a 4 rather than a 5.

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?

Use is only implied: the verb "adds" plus "Acts on one venue, given its address and access key" tells the agent the call creates a new pack for a single venue. There is no explicit when-to-use guidance, no mention of when to prefer update_pack over this, and no preconditions such as existing venue or plan requirements.

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