Skip to main content
Glama
Sign In

Borro

by markets.borro
OverviewDiscussionsAdmin

gAIX loans: the market and a wallet's loan

gaix_market
Read-onlyIdempotent

Borrowing USDG against Goldstein's gAIX (a tokenized index fund of AI and tech stock tokens): the price Borro lends at (what a share redeems for at Chainlink's stock prices, less the fund's redemption fee), whether borrowing is paused (every weekend, and whenever a basket price is out of date; repaying always works), the limit (LLTV) and the new-loan limit (three quarters of it), what a borrower pays a year from now on, what is free to borrow, and the fund's own NAV as context. With wallet: that wallet's loan (gAIX posted, what it is worth, what is owed, how much of the limit is used, what it can still borrow, the price at which it can be liquidated) and its gAIX and USDG.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gaix_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletNoOptional: a wallet whose loan to read (0x...)

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?

Annotations already cover the read-only/idempotent safety profile, and the description adds substantial domain behavior beyond them: borrowing is paused every weekend and whenever a basket price is stale, repaying always works, the new-loan limit is three quarters of LLTV, and the borrow price nets out the fund's redemption fee. It does not discuss latency, caching of prices, or failure modes when a wallet is unknown, which keeps it out of 5 territory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Everything stated earns its place, but it is delivered as one enormous run-on sentence with nested parentheses, so the reader must re-parse to separate market fields from wallet fields. Breaking it into a market sentence and a wallet sentence would improve scannability without losing content.

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 must carry the return payload, and it does: it enumerates every returned market figure and every wallet-level figure including liquidation price. Given the tool's moderate complexity, an agent could call it correctly from this text alone; only the response shape/units (percent vs. absolute, token decimals) remain unstated.

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% and the single parameter is already documented as 'Optional: a wallet whose loan to read'. The description still adds meaning by enumerating exactly what the wallet branch returns (gAIX posted, its value, debt, limit used, remaining borrow capacity, liquidation price) plus the wallet's gAIX and USDG balances, which the schema does not say.

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?

The description names the specific resource set: gAIX market parameters (borrow price, pause state, LLTV, new-loan limit, borrow rate, free liquidity, NAV) plus a wallet's loan and balances when a wallet is supplied. That is concrete and distinguishable from write siblings like gaix_borrow and gaix_repay. It only falls short of a 5 because the opening is a long noun-phrase rather than a clean verb+resource statement.

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 rather than stated: it is evidently the read-before-acting tool for the gaix_borrow/gaix_lend/gaix_repay family and for checking pause state, but the description never says 'call this before borrowing' or names any alternative reading tool. There are no exclusions, so the agent must infer the when-to-use from the sibling names.

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