Skip to main content
Glama

SAP MCP Server

by ai.oobeprotocol.sap.mcp

Plan Premium Session

sap_premium_session_start

Free premium session planner. Creates a bounded session plan for a stream, webhook, or premium tool capability before any x402 charge. Use it to validate plugin id, capability id, requested units, TTL, provider readiness, and estimated price; paid activation happens only on the delivery rail.

SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. 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
consumerNoOptional runtime, agent id, wallet, or application identifier requesting the premium session plan.
pluginIdYesPremium plugin id from sap_premium_plugin_catalog, for example sap-premium-market-data.
ttlSecondsNoHow long the unpaid planning object should remain valid. Clamped between 60 and 3600 seconds.
maxPriceUsdNoOptional buyer budget cap in USD. Agents should compare this to estimatedPriceUsd before paid activation.
capabilityIdYesCapability id from sap_stream_catalog or sap_webhook_catalog, for example jupiter.quote.delta.
capabilityTypeYesCapability type being planned: stream, webhook, or tool.
requestedUnitsNoRequested paid units for the session. Streams use minutes, webhooks use events, tools use sessions.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionYesPremium session plan. This is a planning object and must be paid/activated by the delivery rail before live data is delivered.
monetizationYesx402/pay.sh payment guidance for the premium stream or webhook activation rail.
providerStatusYesProvider readiness at the moment the session was planned.

TDQS

A4.1/5.0
Behavior4/5

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

Discloses that the tool is free, creates a plan without charging, and validates inputs. Includes SAP MCP routing/pricing guidelines. No contradictions with annotations.

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?

Two paragraphs with clear first sentence. Second paragraph has execution guidance that could be integrated elsewhere, but overall is reasonably concise.

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?

Covers purpose, validation items, and execution context. With an output schema present, description is sufficient for understanding the tool's role in the workflow.

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. Description mentions key parameters (pluginId, capabilityId, etc.) but adds limited additional meaning beyond the schema's own 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 creates a 'bounded session plan' for streams, webhooks, or premium tools before any charge, distinguishing it from activation tools like sap_premium_activate_session.

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?

Explicitly says to use it to validate plugin id, capability, etc., and notes that paid activation occurs later. Execution guidance is provided, but no explicit when-not-to-use or alternatives are given.

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