Skip to main content
Glama

issue_customer_pass

DestructiveIdempotent

Issue a session package sold in person and email its redemption code to the customer. 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": {
      "pass": "<pass>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "issue_customer_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
passYes
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 openWorldHint, idempotentHint and destructiveHint=true; the description adds real value beyond them by disclosing the external side effect (an email with a redemption code is sent to the customer) and by turning idempotentHint into an actionable instruction to reuse the key on retry. It still says nothing about required permissions, whether issuance is reversible, or failure modes after a partial email send.

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, front-loaded with the action and its user-visible effect, followed by the retry rule. Nothing is redundant and no sentence is filler.

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?

Behavioral safety is well covered by the annotations, and the description correctly notes the code is emailed rather than returned (consistent with no output schema). However, for a mutation tool with a nested three-field object and zero schema descriptions, the definition does not tell an agent where the productId originates or what happens on a validation failure.

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 description coverage is 0%, so the description must carry meaning for the nested pass object and the idempotency key. It does explain the idempotencyKey's purpose (retry) and implies name/email are the customer's details, but it never explains what productId identifies or whether it comes from a separate catalog lookup, leaving one of three nested fields uninterpreted.

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?

Specific verb+resource: "Issue a session package sold in person and email its redemption code." That clearly separates it from list_customer_passes / record_customer_pass_use, but it never names the nearest sibling (issue_gift_card) so the distinction is inferred from the resource noun only.

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?

"Sold in person" implies a channel condition and the retry sentence gives concrete guidance on repeat calls. There is no explicit when-not-use statement or named alternative for the gift-card vs pass choice, so an agent must infer routing.

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