Skip to main content
Glama
Sign In

Borro

by markets.borro
OverviewDiscussionsAdmin

Prepare: take gAIX out of bgAIX

gaix_withdraw
Read-onlyIdempotent

Unsigned transactions to take gAIX out of bgAIX back to the wallet (amount, or all: true), as much as is not lent out to shorts right now. Simulated from the wallet.

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": "gaix_withdraw"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNotrue closes or takes out everything
amountNogAIX to take out, as a decimal string
walletYesThe wallet's address (0x...); the transactions are built for it to sign

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: the result is an unsigned transaction set, not a state change, and the withdrawal may be partial because only funds 'not lent out to shorts right now' are available. That partial-fill caveat is exactly the kind of behavior an agent needs. It does not mention signer/approval flow or failure behavior when the request exceeds availability.

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?

A single, dense sentence with the destination and inputs front-loaded and no filler. Every clause carries information, though 'Simulated from the wallet' is slightly compressed and could be clearer about how the amount is computed.

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?

With no output schema, the description correctly states that the return is unsigned transactions, and it discloses the liquidity constraint that can shrink the amount. Remaining gaps (signing/approval requirement, behavior when amount exceeds available liquidity) are minor for a prepare-style tool.

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 all three parameters are already documented in the schema, including 'all' and 'amount' as decimal string. The description restates the amount-or-all:true choice without adding format or precedence rules (e.g. what happens if both are supplied), so the baseline 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?

States a specific verb+resource pair: 'Unsigned transactions to take gAIX out of bgAIX back to the wallet', with the source and destination pools named. It does not name a competing sibling (e.g. gaix_short_close_in_kind or gaix_lend) to route against, so it stops short of a 5.

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?

Usage context is implied by the 'take out of bgAIX back to the wallet' framing plus the amount-vs-all choice, but there is no explicit when-to-use/when-not-to-use guidance or a named alternative for related movements (gaix_lend, gaix_short_close_in_kind).

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