Skip to main content
Glama

gage

by cash.gage
OverviewDiscussionsAdmin

Borrow quote

gage_borrow_quote
Read-onlyIdempotent

The largest loan the partner vaults fund now for at most maxCollateral of a token, or one exact loan (collateral and principal) priced as gage.cash prices it, in USDG or the lend asset named, with a prepare object for gage_prepare_borrow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesLoan term in seconds, one of the terms gage_capabilities lists
tokenYes
walletNo
lendAssetNoThe asset the loan is paid in and repaid in: USDG when omitted, or a lend asset gage_capabilities lists (its token address)
principalNoWith collateral: the exact amount to borrow, raw units of the loan's asset; priced as the borrow card prices it
collateralNoWith principal: the exact pledge of one chosen loan, raw units
maxCollateralNoMost of the token to pledge, raw units: quotes the largest loan the vaults fund for it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / collateral
      Added value: +{
+  "description": "With principal: the exact pledge of one chosen loan, raw units",
+  "pattern": "^[1-9]\\d{0,77}$",
+  "type": "string"
+}
    • changedInput schema / properties / maxCollateral / description
      Previous value: -"Most of the token to pledge, raw units"New value: +"Most of the token to pledge, raw units: quotes the largest loan the vaults fund for it"
    • addedInput schema / properties / principal
      Added value: +{
+  "description": "With collateral: the exact amount to borrow, raw units of the loan's asset; priced as the borrow card prices it",
+  "pattern": "^[1-9]\\d{0,77}$",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "token",
-  "maxCollateral",
-  "term"
-]New value: +[
+  "token",
+  "term"
+]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds useful context that quotes reflect what vaults 'fund now' and that the output is a prepare object for gage_prepare_borrow, but it doesn't disclose freshness/liveness guarantees or how the two quote modes are returned. Adequate but not rich.

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?

It is a single very long run-on sentence that front-loads one quote mode ('The largest loan...') rather than the tool's core identity. It packs substantial meaning but is hard to parse at a glance, so structure works against 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?

With no output schema, the description carries the burden of explaining what is returned, and it does: the largest fundable loan or an exact loan, denominated in USDG or the lend asset, plus a prepare object for gage_prepare_borrow. Combined with the schema, this is close to sufficient for calling the tool correctly, though the wallet parameter's role is never addressed.

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 71%, and the description meaningfully supplements it by explaining the two mutually exclusive modes: maxCollateral yields 'the largest loan the partner vaults fund', while collateral plus principal yields 'one exact loan'. It also clarifies lendAsset behavior (USDG when omitted or the named lend asset). token and wallet remain undocumented, but the mode semantics are genuinely additive.

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 conveys that this is a borrow quote tool that returns either the largest fundable loan for a given maxCollateral or one exact loan priced as gage.cash prices it, and it explicitly names the downstream sibling gage_prepare_borrow. It is a dense run-on rather than a clean verb+resource statement, but an agent can distinguish it from gage_prepare_borrow and gage_leverage_quote.

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 only implied through the phrase 'with a prepare object for gage_prepare_borrow', suggesting a quote-then-prepare pipeline, but there is no explicit when-to-use, when-not-to-use, or comparison against the sibling quote tool gage_leverage_quote. The agent must infer the workflow.

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

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