Skip to main content
Glama

Second Wind AI

Recover a purchased result

recover_purchase
Read-onlyIdempotent

Return the result of a completed purchase again, at no cost. Needs the paymentId and the private recoveryToken from the original delivery.

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": {
      "paymentId": "<paymentId>",
      "recoveryToken": "<recoveryToken>"
    },
    "name": "recover_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentIdYespaymentId from the delivered result
recoveryTokenYesrecoveryToken from the delivered result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the call is free ('at no cost') and requires a private credential (recoveryToken), which implies an authorization check that annotations do not express.

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 cost model, then the prerequisites. Nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-output-schema tool this is nearly complete; the only gap is that the return payload is described only generically as 'the result', so an agent cannot anticipate the shape of what comes back. Given the low complexity, that is a minor omission rather than a blocking one.

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?

The description names both parameters and their provenance ('from the original delivery'), but the schema already documents both at 100% coverage with nearly identical wording ('from the delivered result'). It adds marginal meaning — chiefly that the token is private and must come from the original delivery — but nothing about format or lifetime.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — 'Return the result of a completed purchase again' — and adds the key qualifier 'at no cost', which explains the 'recover' framing in the name. It is unambiguous and clearly distinct from the unrelated AWS-diagnostics siblings.

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 only implied: the agent learns it needs a paymentId and a private recoveryToken from the original delivery, which tells it what to have on hand but not when to prefer this over re-purchasing or contacting support. There are no explicit when-not conditions, though the 'again, at no cost' phrasing does signal the intended re-fetch scenario.

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