Skip to main content
Glama

SAP MCP Server

by ai.oobeprotocol.sap.mcp

sap adrena build open long

sap_adrena_build_open_long

Build an unsigned transaction to open or increase a long perp position on Adrena only after policy, balance, oracle-readiness, and simulation checks pass. Returns transactionBase64 for local signing via sap_payments_finalize_transaction only when safeToApprove=true and approvalBlocked=false. If oracleReadiness.ready=false, simulationError, safeToApprove is not true, or approvalBlocked appears, do not show approval and do not call finalize.

SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesPosition owner wallet public key (base58). This is the fee payer and signer.
leverageYesLeverage multiplier (e.g. 3 = 3x).
priceUsdNoOptional limit price in USD. Omit for market order.
principalTokenYesAsset to trade (long). Supported: JITOSOL, WBTC, BONK.
collateralTokenYesCollateral token. Must match principal for longs. Supported: JITOSOL, WBTC, BONK.
collateralAmountYesCollateral amount in human-readable units (e.g. 10 = 10 JITOSOL).
stopLossPriceUsdNoOptional stop-loss price in USD. When provided, the policy engine treats this trade as having a stop loss. Omit to skip the SL requirement (if policy requires SL, this field must be present).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesMCP content blocks returned to the caller.
isErrorNoTrue when the tool result represents an application-level error.

TDQS

A4.4/5.0
Behavior5/5

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

The description goes well beyond the annotations by explaining that the tool returns transactionBase64, that approval must be gated on safeToApprove and approvalBlocked, and that oracle readiness, simulation errors, and approval blocking must be respected. It also discloses the signer boundary and that hosted builders never receive keypair bytes.

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

Conciseness4/5

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

The description is well-organized with safety behavior first and labeled execution guidance second. It is appropriately sized for a complex builder tool, though there is minor redundancy between 'estimate first' and the routing instruction, and the execution-guidance paragraph repeats the unsigned-builder concept from the opening sentence.

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

Completeness5/5

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

Given the tool's complexity, the description covers the full call lifecycle: preconditions, return conditions, failure handling, payment routing, and local signing requirements. The output schema exists and the 100% parameter schema coverage covers the fields, so no essential invocation behavior is missing.

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 description coverage is 100%, so the baseline is 3. The tool description itself does not add parameter-level meaning beyond what the schema already provides; it focuses on behavior and execution flow rather than clarifying individual fields.

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 opens with a specific action: 'Build an unsigned transaction to open or increase a long perp position on Adrena' and further labels it as an 'unsigned transaction builder.' This cleanly distinguishes it from direct execution tools and from close/short sibling builders.

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

Usage Guidelines4/5

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

The description explicitly states when to use the tool ('only after policy, balance, oracle-readiness, and simulation checks pass') and when not to proceed ('do not show approval and do not call finalize' on the listed failure conditions). It also gives a payment/routing sequence. However, it does not explicitly differentiate from sibling tools like sap_adrena_build_close_long or sap_adrena_build_open_short, and it references sap_payments_finalize_transaction and sap_payments_call_paid_tool, which are not visible in the sibling tool list.

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

All SAP MCP Server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation4/5

Tools are organized by protocol prefix (e.g., adrena_, jupiter_, sap_) which helps distinguish domains. Within each protocol, tool names clearly indicate actions (e.g., openPosition, getQuote). However, with 360 tools, some cross-protocol overlaps (e.g., multiple swap tools) and many similar fetch tools in the sap_* family require careful reading of descriptions to disambiguate.

Naming Consistency4/5

Each protocol group follows a consistent naming convention (e.g., snake_case for adrena_, camelCase for 3land, sap_ prefix for SAP SDK tools). The mix of conventions across protocols is acceptable, though a uniform style would improve predictability. Minor inconsistency: hyphenated names like metaplex-nft_ vs underscores.

Tool Count2/5

360 tools is far too many for a well-scoped MCP server. This aggregates dozens of protocols and SAP-specific features, making navigation difficult. The server would benefit from being split into focused micro-servers (e.g., SAP identity, Jupiter DEX, NFT tools). The current count overwhelms the coherence of the set.

Completeness4/5

The tool set covers a vast range of Solana ecosystem activities: token operations, swaps, staking, NFT management, bridging, oracle data, identity registration, chat, escrow, subscriptions, and premium streaming. Major lifecycle operations are present, though some niche subdomains may have missing functions (e.g., detailed governance or lending management). Overall, it's comprehensive for the intended scope.

Resources