Skip to main content
Glama

update_gift_card_sales_settings

DestructiveIdempotent

Enable or disable gift card sales on the approved business booking page.

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": {
      "enabled": "<enabled>"
    },
    "name": "update_gift_card_sales_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the agent knows this is a mutating, repeatable, non-destructive-to-data-but-impactful toggle. The description adds the affected surface (booking page gift card sales) but does not explain the consequence of disabling — e.g., whether existing issued gift cards remain redeemable or whether in-flight sales are blocked — which is the main behavioral question for a destructiveHint tool.

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?

A single sentence with the action and the target surface front-loaded and zero filler. Nothing is redundant or buried.

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 one-boolean settings toggle with no output schema, the description covers the essentials and annotations carry the safety profile. It falls short on the downstream effects of toggling off and on any permission requirement, which matter given destructiveHint=true.

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?

Schema coverage is 0%, but there is only one boolean parameter whose meaning is fully conveyed by the description's 'enable or disable' phrasing. An agent needs nothing more to supply 'enabled' correctly, so the description effectively compensates for the undocumented schema.

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 specific verb pair ('enable or disable') and a specific resource ('gift card sales'), plus the scope ('on the approved business booking page'). It clearly contrasts with the read-only sibling get_gift_card_sales_settings by implication, though it never names an alternative explicitly.

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 implied by the verb: call it to turn gift card sales on or off. The phrase 'approved business booking page' hints at a prerequisite (the business must be approved), but there is no explicit when-to-use/when-not-to-use guidance, no mention of checking current state via get_gift_card_sales_settings first, and no stated exclusions.

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