Authoryze

Report what happened at checkout

report_purchase_outcome

DestructiveIdempotent

REQUIRED after every checkout attempt with a card from retrieve_card. Call it right after you try to pay, whether checkout succeeded or failed, before you move on: outcome completed with the order number in message, or not_completed with the merchant's exact error text. Don't skip it because checkout went through. Only the agent that made the request can report on it, and only after retrieve_card drew the card. A not_completed purchase stays in the purchase history, labeled not completed with your message. Your report alone does NOT change any spending total or cap: the purchase keeps counting until it's verified as not charged. For a Privacy.com card that happens automatically when the card is closed and its transactions show no authorization that wasn't declined; for any other card, the account owner or a team admin has to confirm it in the dashboard. Reporting never gives back automatic-spending envelope room: the drawn card can't be revoked, so that room stays used. A Privacy.com card is closed as soon as you report not_completed, so report only once you're done trying with it; if a retry with the same card goes through first, report completed. A purchase reported completed can't be changed to not_completed. Reporting the same outcome again is harmless.

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": {
      "request_id": "<request_id>",
      "outcome": "<outcome>",
      "message": "<message>"
    },
    "name": "report_purchase_outcome"
  }
}

Input Schema

Name	Required	Description
`message`	Yes	What happened, in a sentence. For not_completed, include the decline or error text the merchant showed (e.g. 'Your card was declined (insufficient funds)'). For completed, an order number if there is one.
`outcome`	Yes	completed: the merchant took the payment. not_completed: checkout didn't go through.
`request_id`	Yes	The request_id returned by request_purchase

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026
- addedInput schema / properties / request_id / format
```
Added value: +"uuid"
```
- addedInput schema / properties / request_id / pattern
```
Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
```
AddedOct 8, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Far beyond the annotations, it discloses authorization scoping (only the requesting agent, only after retrieve_card drew the card), persistence effects (not_completed stays in history labeled as such), and that the report alone does not alter spending totals or caps. It spells out the verification path for Privacy.com cards versus other cards and states that envelope room is never returned because the drawn card cannot be revoked.

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?

The mandatory-call requirement is front-loaded and every sentence carries operational content. There is minor redundancy — 'Don't skip it because checkout went through' overlaps with the earlier 'whether checkout succeeded or failed,' and 'Reporting the same outcome again is harmless' duplicates idempotentHint.

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 an irreversible, destructive mutation this covers consequences, verification, and idempotency thoroughly. The one omission is the response shape: with no output schema, the description never says what a successful report returns, so an agent cannot anticipate confirmation or verification status.

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 coverage is 100%, so the schema already documents all three parameters including the outcome enum and message content rules. The description's 'order number in message' and 'merchant's exact error text' largely restate the schema's own parameter descriptions, adding little new semantics. Baseline 3 applies when the schema carries the load.

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 names a specific verb and resource — reporting the outcome of a checkout attempt made with a card from retrieve_card — and enumerates the two outcome states. An agent can distinguish it from retrieve_card and request_purchase without inspecting either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Timing is explicit: 'right after you try to pay, whether checkout succeeded or failed, before you move on,' plus the exclusion 'Don't skip it because checkout went through.' It also resolves the retry edge case (if a retry with the same card succeeds first, report completed) and warns not to report not_completed until done trying.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Authoryze tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.