Skip to main content
Glama

Pause or resume a coupon

set_coupon_active
Destructive

Pauses a coupon (it stops applying) or resumes it. Packs already bought with it 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>",
      "coupon_id": "<coupon_id>",
      "active": "<active>"
    },
    "name": "set_coupon_active"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description adds genuinely useful context beyond them: pausing only stops future application and 'Packs already bought with it are not affected', which reassures an agent that past purchases survive. It still omits permission requirements, whether pausing is instantly reversible, and what happens to in-flight redemptions, so it is not a 5.

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 action and immediately followed by the side-effect caveat. The closing sentence about venue, address and access key mostly repeats the schema, but it does establish single-venue scope, so it earns most of its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, four-required-parameter mutation with no output schema, the description covers effect and blast radius but leaves the meaning of the active flag, permission requirements, and the result of the call unaddressed. Adequate to select the tool, thin for invoking it confidently.

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 50%: address and access_key are documented in the schema, and the description only echoes them ('given its address and access key'). The critical mapping of the boolean 'active' parameter to pause vs. resume is left implicit, and coupon_id gets no explanation at all.

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 gives a concrete verb pair and resource ('Pauses a coupon ... or resumes it') plus the observable consequence ('it stops applying'), which is more than a restatement of the name. It does not explicitly contrast with siblings like create_coupon or set_pack_visibility, so it stops short of 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?

Usage is only implied: the reader infers this is the tool for temporarily disabling a coupon without deleting it. There is no explicit statement of when to prefer this over deleting or recreating a coupon, and no preconditions or exclusions beyond the venue-scope sentence.

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