Skip to main content
Glama

Activate or deactivate a pack

set_pack_visibility

visible = false deactivates a pack: it is hidden and can no longer be bought; members who have it keep it. visible = true activates it again. This is the safe way to stop selling a 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>",
      "pack_id": "<pack_id>",
      "visible": "<visible>"
    },
    "name": "set_pack_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
pack_idYes
visibleYes
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only establish that this is a non-read-only, non-destructive, open-world=false mutation; the description goes well beyond that by disclosing the actual consequences — the pack becomes hidden, cannot be bought, and is retained by existing members — plus the fact that the change is reversible. Auth is covered only obliquely via 'given its address and access key', and there is no mention of side effects on listings or pricing or of any rate limits.

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 sentences, all load-bearing, with the highest-value semantics (what visible=false does) front-loaded before the reverse case and the venue scoping note. Nothing is repeated from the title or schema, and there is no filler.

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 mutation with no output schema, the description covers effect, reversibility, and per-venue scope, which is what an agent needs to act safely. The gap is pack_id (undocumented) and the absence of any indication of what a successful call returns or how missing/invalid packs are reported.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 50% schema coverage, the description carries real weight and does so for the most important parameter: it defines exactly what visible=true and visible=false mean in business terms, which the bare boolean in the schema does not. The address/access_key pairing is clarified as venue scoping, but pack_id remains entirely undocumented in both schema and description.

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 specific operation and its two directions, spelling out the effect of each: visible=false hides the pack and blocks purchases while existing members keep it, visible=true reactivates. It implicitly separates itself from a hard removal with 'This is the safe way to stop selling a pack', though it never names delete_pack, so the sibling differentiation is inferential rather than explicit.

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

Usage Guidelines4/5

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

'This is the safe way to stop selling a pack' gives a clear condition for choosing this tool over a destructive alternative, and the reactivation sentence covers the inverse case. It stops short of naming the alternative tool or stating explicit exclusions (e.g., when to use delete_pack instead), so the agent must infer the counterpart.

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