Skip to main content
Glama
OOBE-PROTOCOL

SAP MCP Server

drift_borrow

Borrow tokens on the Drift protocol using deposited collateral as security. Specify wallet, token mint, raw amount, and optional sub-account.

Instructions

Borrow tokens on Drift against deposited collateral.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintYesToken mint address (base58)
amountYesRaw token amount (smallest unit)
walletYesSolana public key (base58)
subAccountIdNo
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions 'against deposited collateral' but fails to explain consequences like changing collateral ratios, interest accrual, or error conditions. The minimal description does not suffice.

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?

The description is extremely concise (one sentence), but it sacrifices necessary detail. While brevity is valued, the lack of crucial information lowers the score.

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?

Given no output schema and only partial parameter coverage, the description is incomplete. It fails to explain the borrowing mechanism, return values, or how it fits with sibling tools like drift_deposit and drift_withdraw.

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?

The schema covers 75% of parameters (subAccountId lacks description), but the description adds no extra meaning beyond the schema. It does not clarify how 'mint' and 'amount' relate to borrowing or what 'subAccountId' signifies.

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 action ('borrow tokens'), the platform ('Drift'), and the condition ('against deposited collateral'). It effectively distinguishes from sibling tools like drift_deposit and drift_lend by specifying the borrowing action.

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

Usage Guidelines2/5

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

The description provides no guidance on prerequisites (e.g., needing to deposit collateral first), when to use vs. alternatives, or when not to use. This lack of context hinders correct tool selection.

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/OOBE-PROTOCOL/sap-mcp'

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