Skip to main content
Glama

issue_gift_card

DestructiveIdempotent

Issue a gift card sold in person and email its redemption code to the recipient. Reuse the same idempotency key on retry.

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": {
      "card": "<card>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "issue_gift_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYes
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and openWorld=true; the description adds value beyond them by disclosing the external side effect (an email with the redemption code is sent to the recipient) and by spelling out the retry contract. It does not explain what makes the operation destructive, whether funds are charged immediately, or whether issuance is reversible.

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 sentences with zero waste: the action and side effect come first, the retry contract second. Every sentence earns 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 financially consequential mutation with no output schema and no schema-level field documentation, the definition covers the retry path but leaves key gaps: amount units and limits, whether the card is active on issue, and what happens on invalid email or failed delivery. Adequate but not complete for the tool's complexity.

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

Parameters2/5

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

Schema description coverage is 0% across two params with a nested card object containing five leaf fields, so the description must carry the burden and largely does not. It never explains that amount is an integer with min/max bounds (implying a minor-unit currency), nor clarifies recipientEmail as the delivery destination versus recipientName/message as personalization.

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?

States a specific verb and resource ("Issue a gift card") plus a scoping qualifier ("sold in person") and a side effect (emailing the redemption code). It does not explicitly name or differentiate from siblings like issue_customer_pass or redeem_gift_card, so it falls short of full sibling differentiation.

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?

Gives a clear usage context – in-person sales – and adds operational guidance to reuse the idempotency key on retry, which is a genuine when/how instruction. It stops short of naming alternatives or stating when not to use it (e.g. online/API sales).

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