Skip to main content
Glama
Launch-On-Basis

Basis MCP Server

Official

leverage_buy

Open a leveraged long position on any token using USDB collateral. No price liquidation – time-based only. Simulate first, then confirm execution.

Instructions

Open leveraged position. NO price liquidation — time-based only. Simulates first, requires confirm=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesToken name or address
amount_usdbYesUSDB collateral
daysYesLoan duration (10-1000)
confirmYesMust be true to execute
Behavior4/5

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

With no annotations, the description carries the burden. It discloses no price liquidation (time-based only), simulation first, and confirm=true requirement. This adds significant behavioral context beyond the schema.

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?

Three concise sentences, front-loaded with the main action. Every sentence adds value with no wasted words.

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?

For a leveraged position tool with no output schema and no annotations, the description covers core functionality, simulation, and confirmation. Could mention fees or execution details, but overall adequate.

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 baseline is 3. The description does not add additional meaning to parameters beyond what the schema already provides. It only restates that confirm must be true.

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?

The description clearly states the tool opens a leveraged position. It specifies key features: no price liquidation, time-based only, simulation, and confirmation requirement. This distinguishes it from related tools like close_leverage.

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 description implies usage for opening a leveraged position but does not explicitly guide when to use this tool versus alternatives like close_leverage or extend_loan. No when-not-to-use or prerequisites provided.

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/Launch-On-Basis/MCP-TS'

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