Skip to main content
Glama

Claim store credit for a purchase

claim_refund
Destructive

Claim store credit for a purchase that did not work, within 24 hours; one claim per order. We verify on our side (our own test run or our service logs) before crediting; test_output and detail are kept on file, but only our records decide. The answer says credited or rejected, and why. Once credited, a kit gives no more download links and a utility loses that order's paid time. Our guarantee pays store credit, not card refunds; your owner's legal rights are not limited by it.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "detail": "The kit tests fail on a clean install.",
      "order_id": "ord_exampleexampleexample2"
    },
    "name": "claim_refund"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoWhat did not work, in plain words.
order_idYesorder_id (ord_...) from buy or list_orders.
test_outputNoFor a kit: the failing test output.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / order_id / description
      Previous value: -"Order id from buy (order_id)."New value: +"order_id (ord_...) from buy or list_orders."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "detail": "The kit tests fail on a clean install.",
      +    "order_id": "ord_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  3. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  4. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / detail / description
      Added value: +"What did not work, in plain words."
    • addedInput schema / properties / order_id / description
      Added value: +"Order id from buy (order_id)."
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
    • addedInput schema / properties / test_output / description
      Added value: +"For a kit: the failing test output."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: it discloses the verification process (their own test run or service logs), that submitted evidence is retained but not decisive, the response shape (credited or rejected, with reason), and the concrete consequences of success, namely a kit loses download links and a utility loses that order's paid time. That is exactly the post-claim state an agent needs before invoking a destructive, non-idempotent tool.

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?

Front-loaded with the claim itself, then consequences, then scope limitations, so the most important information arrives first. It is dense semicolon-chained prose with some run-on sentences, but essentially every clause carries decision-relevant content.

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

Completeness5/5

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

For a destructive mutation with no output schema, the description covers the trigger conditions, the verification model, the outcome vocabulary, and the irreversible side effects. An agent has everything needed to decide whether to call it and what to expect afterwards.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic weight by explaining that test_output and detail are kept on file yet only internal records decide the outcome, which tells the agent these are evidentiary rather than authoritative. The passport_token fallback is left entirely to the schema.

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?

States a specific verb and resource ("Claim store credit for a purchase that did not work") and immediately scopes it against the nearest confusion: "Our guarantee pays store credit, not card refunds." An agent can tell this apart from a payment-refund tool without further reading.

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 concrete eligibility conditions: the purchase must not have worked, it must be within 24 hours, and only one claim per order. It also implicitly excludes card refunds. It does not name a sibling tool or say what to do if the window has passed, which keeps it short of a 5.

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.