Skip to main content
Glama

new_crypto_loan_flexible_borrow

Borrow cryptocurrencies flexibly against your crypto collateral. Specify loan currency and amount to initiate a flexible loan.

Instructions

Borrow via flexible crypto loan.

Args: loan_currency: Loan currency. loan_amount: Loan amount.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loan_currencyYes
loan_amountYes
Behavior1/5

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

The description gives no behavioral information beyond the action of borrowing. It does not disclose whether the operation is destructive, requires specific permissions, has rate limits, or any side effects. With no annotations provided, the description completely fails to inform the agent about behavioral traits.

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

Conciseness2/5

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

The description is extremely short, but this brevity comes at the cost of missing essential information. While front-loaded, it does not earn its place as it omits usage guidance, parameter details, and behavioral context.

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

Completeness1/5

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

Given the complexity of the domain (many sibling loan tools), no annotations, and lack of output schema, the description is severely incomplete. It fails to provide any context about prerequisites, return values, or how this tool fits into the broader workflow.

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

Parameters1/5

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

Schema description coverage is 0%, and the description only lists parameter names ('loan_currency', 'loan_amount') without any additional context such as format, allowed values, or examples. It adds no value beyond the schema, failing to compensate for the lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Borrow via flexible crypto loan,' which clearly identifies the verb and resource. However, it does not explicitly distinguish it from sibling tools like new_crypto_loan_fixed_borrow, relying on the tool name for differentiation. The purpose is clear but lacks specificity about what a 'flexible' loan entails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as new_crypto_loan_fixed_borrow or other lending-related tools. There are no exclusions, prerequisites, or context about required conditions (e.g., existing loan or collateral).

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

Install Server

Other Tools

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/JohnnyWic/bybit-mcp'

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