Skip to main content
Glama
Sign In

Borro

by markets.borro
OverviewDiscussionsAdmin

Prepare: lend gAIX to the shorts

gaix_lend
Read-onlyIdempotent

Unsigned transactions to lend gAIX from the wallet into bgAIX, the vault that lends it to gAIX shorts: approve the gAIX (when needed), deposit. What it earns moves with use. 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>",
      "amount": "<amount>"
    },
    "name": "gaix_lend"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesgAIX to lend, as a decimal string, like "10"
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.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely useful context beyond them: the output is unsigned transactions for the wallet to sign, a conditional approve step is included, and the result is 'simulated from the wallet.' It does not contradict readOnlyHint, since the tool builds transactions rather than executing them. The vague line 'What it earns moves with use' is the one piece that adds little clarity.

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?

Compact and front-loaded: the action and destination come first, then the mechanics, then the signing caveat. Only 'What it earns moves with use' is loose filler that could be tightened or made concrete.

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 two-parameter transaction-builder with no output schema, the description supplies the essential missing pieces: that the return is unsigned transactions, that an approve may be bundled, and that it is simulated. A brief note on the resulting position or token representation (bgAIX receipt) would fully close the gap.

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 both 'amount' and 'wallet' are already documented in the schema. The description reinforces that the transactions are built for the supplied wallet and that amount is gAIX to lend, but adds no format or edge-case detail beyond the schema's own notes.

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 ('lend gAIX from the wallet into bgAIX') and explains the vault's role ('lends it to gAIX shorts'), which distinguishes it from siblings like gaix_withdraw and the gaix_short_* family. It also enumerates the two on-chain actions produced (approve, deposit).

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 is implied by the framing as the supply-side counterpart to gAIX shorts, but there is no explicit when-to-use/when-not guidance or direct routing to alternatives such as gaix_withdraw for exiting. An agent can infer intent but must reason about it rather than read it.

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