SAP MCP Server

SAP Perp Trade Plan

sap_perp_trade_plan

Create a trader-grade perpetual futures plan from a simple intent. Returns notional size, stop risk, reward/risk, liquidation estimate, preflight checklist, and the exact SAP MCP read tools to call next. This is analysis-only: SAP MCP does not expose Adrena execution builders until they are IDL-backed and locally finalizable. Required fields: market, side, collateralAmountUsd, leverage, entryPrice. Get entryPrice from sap_adrena_get_trading_prices or sap_adrena_get_prices before calling this tool.

SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: priced by hosted x402 challenge. 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

Name	Required	Description
`side`	Yes	Intended direction for the trade.
`notes`	No	Optional user notes, catalyst, invalidation thesis, or strategy context.
`market`	Yes	Perp market symbol or pair, for example SOL-PERP, BTC-PERP, or ETH-PERP.
`leverage`	Yes	Requested leverage multiplier. Keep conservative unless user policy explicitly allows more.
`timeframe`	No	Trading horizon such as scalp, intraday, swing, or hedge.
`entryPrice`	Yes	Reference entry price in USD used for risk math. Required. Get the current price from sap_adrena_get_trading_prices or sap_adrena_get_prices before calling this tool.
`stopLossPrice`	No	Optional stop loss price in USD. Strongly recommended before execution.
`maxSlippageBps`	No	Maximum execution slippage in basis points. Default 50 bps.
`takeProfitPrice`	No	Optional take profit price in USD used to compute reward/risk.
`maxAccountRiskPct`	No	Maximum account risk percentage allowed by local policy. Default 1%.
`collateralAmountUsd`	Yes	Collateral to allocate in USD. This is the margin budget, not notional size.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`content`	Yes	MCP content blocks returned to the caller.
`isError`	No	True 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 details that the tool is 'analysis-only' and provides execution guidance on pricing, routing, and signer boundaries. This goes beyond annotations (readOnlyHint=false, destructiveHint=false) by explaining what the tool does not do (execution) and what limitations exist.

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 lengthy (multiple paragraphs) and includes execution guidance that could be more efficiently placed elsewhere or referenced. It is organized but not as concise as it could be for a tool that should be quickly understood.

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?

Given the tool's complexity (11 parameters, 5 required), the description covers prerequisites, outputs, and execution context. It explains when to call this tool (before execution) and what to do next (call read tools). The presence of an output schema (implied by context) reduces need to describe return values.

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

Parameters4/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 adds value by explaining that entryPrice must be fetched from specific tools and that collateralAmountUsd is 'margin budget, not notional size.' This clarifies parameter meaning beyond the schema descriptions.

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's purpose: 'Create a trader-grade perpetual futures plan from a simple intent.' It lists specific outputs (notional size, stop risk, etc.) and explicitly notes it is 'analysis-only', distinguishing it from execution tools like sap_adrena_build_* siblings.

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 specifies required fields and tells the agent to get entryPrice from sap_adrena_get_trading_prices or sap_adrena_get_prices before calling. It also explains that SAP MCP does not expose execution builders until IDL-backed, implying this tool is for planning only. However, it does not explicitly contrast with alternative tools like sap_adrena_trade_intent or other build tools.

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 tools Inspect

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.

SAP Perp Trade Plan

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources