Skip to main content
Glama

set_coupon_active

Turn a discount code on or off (codes are never deleted, only switched off). (confirm-gated: previews until confirm: true)

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": {
      "id": "<id>",
      "isActive": "<isActive>"
    },
    "name": "set_coupon_active"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
isActiveYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description reinforces that with the substantive fact that codes are never deleted, only switched off — telling the agent the operation is reversible and no data is lost. The confirm-gating note adds the two-phase preview/execute behavior, though that partially duplicates the schema's description of the confirm parameter, keeping this short of 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.

Conciseness5/5

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

Two short clauses, both front-loaded: the core operation and the reversibility guarantee come first, and the confirm-gate caveat follows. No filler or redundant restatement of the tool name.

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 simple single-record toggle with no output schema, the description covers the essentials an agent needs: what changes, that nothing is deleted, and that execution requires confirm: true. It falls short only in not clarifying the 'id' parameter's nature or what a preview response contains.

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?

Only 33% of the three parameters are documented in the schema (confirm), so the description needs to compensate for id and isActive but does so only implicitly — 'turn a discount code on or off' implies a boolean flag and a target code identifier without stating the identifier format or the exact mapping to isActive. The preview/confirm semantics restated in the description are already fully specified in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('turn ... on or off') and a specific resource ('discount code'), which cleanly separates it from sibling toggles such as set_challenge_active, set_plan_active, and set_webhook_active that act on different resources. An agent can identify the target operation without opening the schema.

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: an agent infers this is the tool for activating or deactivating a coupon, and the parenthetical clarifies the reversible, non-deleting semantics. There is no explicit statement of when to pick this over alternatives (e.g., create_coupon vs. this) or any prerequisite conditions beyond the confirm gate.

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.