Skip to main content
Glama
Sign In

Borro

by markets.borro
OverviewDiscussionsAdmin

Prepare: post gAIX and borrow USDG

gaix_borrow
Read-onlyIdempotent

Unsigned transactions to post gAIX as collateral and borrow USDG against it, from the wallet: approve gAIX to Morpho for exactly what is posted (when needed), post it, borrow. post and amount can each be given alone (post more to an open loan; borrow more against what is posted). Borrowing pauses every weekend and whenever a basket price is out of date (posting does not), and stops at three quarters of the limit. 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_borrow"
  }
}

Input Schema

NameRequiredDescriptionDefault
postNogAIX to post, in whole shares as a decimal string, like "10"
amountNoUSDG to borrow, as a decimal string, like "250"
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.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the operation builds unsigned transactions simulated from the wallet, approves exactly the posted gAIX amount to Morpho only when needed, borrowing pauses on weekends and on stale basket prices while posting does not, and borrowing caps at three quarters of the limit. The 'unsigned transactions' framing is consistent with readOnlyHint=true, since nothing is submitted to chain by the server.

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?

Information-dense and front-loaded: the return type (unsigned transactions) and target (wallet) come first, then parameter optionality, then the pause/cap caveats. A few clauses are tightly packed (the borrowing-pause sentence carries three separate constraints), but there is no filler.

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?

No output schema exists, and the description compensates by naming what is produced — unsigned transactions, simulated from the wallet — so the agent knows nothing is broadcast. For a three-parameter prepare tool, the inclusion of pause conditions, the borrow cap, and the approve step makes it complete enough to call correctly.

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 the schema already documents all three parameters including formats and examples. The description adds the meaningful optionality relationship (either can be supplied alone) and ties the approve amount to 'post', but adds no format or constraint detail beyond the schema — 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 action (unsigned transactions to post gAIX as collateral and borrow USDG) plus the wallet it is built for. It is clearly distinguishable from siblings such as gaix_repay, borrow, gaix_withdraw and supply, and the title/description pair leaves no ambiguity about the asset pair involved.

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?

Explains that 'post' and 'amount' can each be given alone, with parenthetical use cases (top up collateral, borrow more against existing collateral), which is genuine when-to-use guidance. It does not explicitly route the agent to alternatives such as gaix_repay or release_collateral, so it stops short of naming the sibling tool for the opposite operation.

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