Skip to main content
Glama

void_gift_card

DestructiveIdempotent

Void an issued gift card in the approved business and zero its remaining balance. This permanently prevents redemption.

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>"
    },
    "name": "void_gift_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety is largely covered. The description adds genuinely useful context by stating the balance is zeroed and redemption is permanently prevented, making irreversibility explicit. However it omits what happens on a repeat call, on an already-redeemed card, or what permissions/scope are required.

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?

Two tight sentences with the effect and consequence front-loaded and no filler wording. The only structural weakness is that the irreversibility warning is embedded rather than called out separately.

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, idempotent mutation with no output schema, the description covers the outcome well but leaves gaps an agent needs: what the id means, error behavior on already-voided or already-redeemed cards, and permission requirements. It is adequate but not complete for a destructive operation.

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?

With one parameter and 0% schema description coverage, the description carries the burden but says nothing about the id itself. It is unclear whether id is the internal gift-card identifier or the redemption code, which matters a great deal for correct invocation. The single reference to an "issued gift card" only loosely implies what the parameter identifies.

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?

Names a specific verb (void) and resource (issued gift card) plus the concrete effect: zeroing the remaining balance. It does not name siblings like redeem_gift_card or void_event_ticket, so differentiation from adjacent void/cancel tools is left to inference, but the purpose itself is unambiguous.

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

Usage Guidelines2/5

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

The word "issued" hints at a precondition, but there is no explicit when-to-use guidance, no statement about when to prefer redeem_gift_card or a cancel/refund path, and no guidance for cards that are already redeemed or already voided. The agent must infer the usage context entirely.

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