Skip to main content
Glama

quote_borrow

Get pre-sign borrow metrics: health factor, liquidation price, and cap compliance. Validate the loan against Cluby's exact market arithmetic.

Instructions

What a borrow would do before it is signed: health factor, liquidation price, and whether it exceeds the cap the app enforces.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketYes
borrowAmountYesLoan asset in whole units (USDG)
collateralAmountYesCollateral in whole tokens

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It clearly signals a non-executing quote operation and names the expected outputs, which is meaningful transparency for a read-only simulation tool. It could still mention that it does not modify state more explicitly, but the pre-signing framing largely covers this.

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

Conciseness5/5

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

A single, tightly worded sentence that front-loads the purpose and lists the key outputs without any waste. It is immediately scannable and to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, no annotations, and a required under-documented market parameter, the description is too sparse. It names three output concepts but does not describe return shape, parameter constraints beyond schema, or how to handle cap-related errors, leaving an agent without enough information to confidently invoke and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers borrowAmount and collateralAmount semantics, but market has no description. The tool description adds no parameter-level meaning and does not clarify what market refers to, leaving a required parameter under-specified with only 67% schema coverage.

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 clearly indicates that this tool produces a pre-signing quote for a borrow action, listing health factor, liquidation price, and cap compliance. It distinguishes the operation from the sibling quote_multiply by focusing on borrowing rather than multiplying, though it does not explicitly name the alternative.

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?

The phrase 'before it is signed' implies this tool is for simulating a borrow without executing it, which gives useful context. However, it does not explicitly state when to prefer quote_borrow over quote_multiply or other siblings, nor does it mention exclusions.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/clubytech/cluby-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server