Skip to main content
Glama

record_customer_pass_use

DestructiveIdempotent

Record one manually used session on a customer pass. 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": {
      "id": "<id>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "record_customer_pass_use"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the description is not contradictory and its retry/idempotency sentence reinforces the contract usefully. It still omits what actually gets consumed (a session credit), what happens when no sessions remain, and whether a compensating call exists.

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 the primary action first and the retry caveat second. No filler, no repetition of schema or annotations.

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 two-parameter mutation tool with annotation coverage but no output schema, the definition covers the core action and the retry contract. It falls short on the meaning of the required id, the side effect on the pass balance, and failure behavior when the pass is exhausted or the use was already recorded.

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 carries the burden. It adds genuine meaning for idempotencyKey (reuse on retry), but the required "id" parameter is never disambiguated - it is unclear whether it identifies the pass or the use record - which leaves half the parameters semantically unexplained.

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?

"Record one manually used session on a customer pass" gives a specific verb (record), resource (customer pass session), and scope qualifier (manually used, single). It is clearly distinct from reversal/listing siblings, but it never names an adjacent tool such as return_customer_pass_use, so differentiation is inferred rather than stated.

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 "manually used session" - i.e., use this when redeeming a session outside the normal booking flow - and the retry condition is spelled out. However, there is no explicit when-not guidance and no pointer to the sibling that would undo the operation, leaving the agent to infer the boundary.

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