Skip to main content
Glama
Sign In

Borro

by markets.borro
OverviewDiscussionsAdmin

Prepare: take USDG (or a stray token) out of a receiving address

payto_withdraw
Read-onlyIdempotent

An unsigned transaction for the owner to take what waits at its receiving address out to its own wallet: USDG as USDG before it is swept (token USDG, the default), or ETH or another ERC-20 token sent there by mistake (token ETH, or the token's address). amount is a decimal string, or "all" (the default) for whatever is there when it lands. USDG already swept is the wallet's bUSDG: redeem it from the vault with withdraw. Simulated from the wallet; nothing is sent.

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

Input Schema

NameRequiredDescriptionDefault
tokenNo"USDG" (default), "ETH", or a token's address (0x...)
amountNoHow much, as a decimal string, or "all" (default)
walletYesThe wallet's address (0x...); the transactions are built for it to sign

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/destructive/idempotent, but the description adds genuinely non-obvious behavior: 'Simulated from the wallet; nothing is sent,' and that amount 'all' resolves to 'whatever is there when it lands' rather than at build time. It does not cover prerequisites such as ownership or signing requirements beyond 'for the owner to take'.

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 purpose is front-loaded in the first clause and every sentence carries information. The nested parentheticals ('USDG as USDG before it is swept (token USDG, the default)') make the opening sentence heavier than it needs to be, costing some readability.

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 3-parameter prepare-only tool with full schema coverage, annotations, and no output schema, the description covers what is produced (an unsigned transaction), the token and amount defaults, the timing semantics, and the nearest alternative. Only the sweep-vs-withdraw boundary and any signing/ownership preconditions are left implicit.

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; the description goes beyond it by clarifying that 'all' means the balance at execution time and by spelling out that token accepts USDG (default), ETH, or a raw 0x address. That adds real meaning the schema's one-line descriptions do not carry.

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 — building an unsigned transaction that moves funds out of a receiving address into the owner's own wallet — and names the token variants it handles (USDG, ETH, arbitrary ERC-20). It also draws a clear line against the `withdraw` sibling for already-swept bUSDG, so an agent can pick between them without opening a 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 exclusion with the alternative named: 'USDG already swept is the wallet's bUSDG: redeem it from the vault with withdraw.' The phrase 'before it is swept' implies the sweep path but never explicitly routes the agent to payto_sweep, leaving one sibling boundary to inference.

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

All Borro 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