Skip to main content
Glama
Sign In

Xaalis

by org.xaalis
OverviewDiscussionsAdmin

Reclaim from an agent wallet (sandbox)

xaalis_reclaim_agent_wallet
Idempotent

Sandbox: move unreserved money from an agent wallet back to the merchant balance.

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": {
      "wallet_id": "<wallet_id>",
      "amount": "<amount>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "xaalis_reclaim_agent_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount to move back, in whole XOF (F CFA). Integer, no decimals: 5000 = 5 000 F CFA.
wallet_idYesAgent wallet id (aw_…)
idempotency_keyYesStable key for this business action (e.g. order-1042). Reuse the SAME key when retrying; a new key creates a new operation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the safety profile (non-read-only, non-destructive, idempotent, open-world). The description adds one genuinely useful behavior — only the unreserved portion is movable — but says nothing about what happens to the wallet afterwards, partial/empty outcomes, or error conditions when the amount exceeds the unreserved balance.

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?

One short sentence with the environment caveat front-loaded and zero filler. It is efficient, though it is arguably too terse for a money-movement operation.

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 non-destructive but money-moving mutation with no output schema, the agent needs to know the outcome semantics (wallet balance decrease, behavior when unreserved is insufficient, whether the wallet stays active). The description covers the intent but leaves these operationally relevant details unstated.

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 schema itself explains amount units (whole XOF), wallet id format and idempotency-key reuse. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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?

Names a specific verb (reclaim/move), a specific resource (agent wallet) and a concrete destination (merchant balance), plus a scope qualifier ('unreserved'). Together with the direction of movement this clearly contrasts with the sibling xaalis_fund_agent_wallet, though no sibling is named explicitly.

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?

'Sandbox' signals this is a test-environment operation and 'unreserved' implies that reserved funds cannot be reclaimed, but the description never states when to choose this over funding/adjusting a wallet or what to do when the unreserved balance is insufficient.

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

All Xaalis toolsInspect
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.

Resources