Skip to main content
Glama

Prepare escrow release

charges_prepare_release
Read-only

Preview the exact Safe transaction for releasing a charge escrow—destination, token, amount, chain ID, nonce, safeTxHash, and EIP-712 typed data to sign. Read-only; signs and submits nothing.

Instructions

Show the exact Safe transaction an escrow release of this charge would execute: destination, token, amount in base units, chain id, Safe nonce, safeTxHash and the EIP-712 typedData the escrow releaser must sign. Read-only: it signs and submits nothing, and the release itself is not available through this server. Valid only while the escrow's balance is unchanged.

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>"
    },
    "name": "charges_prepare_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA Klappay charge id (`ch_` followed by letters and digits).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with "it signs and submits nothing." It adds non-obvious behavioral context beyond the annotations: the balance-unchanged validity window and the fact that execution is out of scope for this server. It stops short of describing auth requirements or what happens when the balance has changed.

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 sentences, front-loaded with the payload contents, followed by the read-only caveat and validity constraint. Every clause carries information an agent needs; nothing is padding.

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?

With no output schema, the description compensates by enumerating exactly which fields the returned transaction contains. Combined with the safety and validity statements, an agent has everything needed to call this correctly and interpret the result.

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% and the only parameter is fully documented in the schema, including the ch_ pattern. The description only reinforces "this charge" without adding format or lookup semantics beyond the schema, so the baseline 3 applies.

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 ("Show the exact Safe transaction") plus the resource (escrow release of this charge) and enumerates the exact payload fields returned: destination, token, amount in base units, chain id, Safe nonce, safeTxHash, and EIP-712 typedData. This is clearly distinguishable from charges_prepare_refund or charges_get without opening any schema.

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 an explicit precondition ("Valid only while the escrow's balance is unchanged") and clarifies the boundary that the release itself is not available through this server, which routes the agent correctly. It does not name a sibling alternative for the post-signing step, so a 4 rather than a 5.

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