Skip to main content
Glama

SAP MCP Server

by ai.oobeprotocol.sap.mcp

Start SAP MCP Agent Mode

sap_agent_start
Read-onlyIdempotent

Return the concise startup playbook for agents using SAP MCP. Call this when the user says "Start SAP MCP", "Initialize SAP MCP", "Load SAP", or asks what SAP MCP can do.

SAP MCP execution guidance: Intent: agent bootstrap, routing, skills, or repair guidance. 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
goalNoOptional user goal to tailor the startup plan, such as "register an agent", "check wallet balance", or "swap tokens".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesWhether the bootstrap instructions were generated.
serverModeYesCurrent SAP MCP server mode.
paymentFlowYesHow to handle hosted x402/pay.sh paid calls safely.
repairCommandYesWizard command to repair local hosted/profile/payment bridge setup.
hostedEndpointYesCanonical hosted SAP MCP endpoint.
connectionCheckYesHow agents should answer simple connection/status questions.
activationPhrasesYesShort user phrases that should trigger this bootstrap behavior.
userFacingSummaryYesShort text the agent can show the user after startup.
immediateToolCallsYesTool calls the agent should run first when available.
sessionContextPacketYesMachine-readable SAP MCP routing, freshness, memory, proof-tape, and forbidden-action rules for this session.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the tool is safe. Description adds valuable context on costing (free, no x402), routing (keep small/exact), and signer boundary (no keypair bytes on hosted side), which are beyond what annotations provide.

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 front-loaded with the main purpose in the first sentence. However, the second paragraph repeats text from the input schema description (pricing, routing, signer boundary), making it less concise than ideal.

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?

With an output schema present and annotations covering safety, the description covers usage and behavioral traits well. It lacks detail on what the 'startup playbook' actually contains (e.g., format or structure), but the output schema likely fills this gap.

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% for the single 'goal' parameter, and its description is clear. The tool description does not add significant new information beyond what's in the schema, so baseline 3 is appropriate.

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?

Description explicitly states it returns a startup playbook for agents using SAP MCP. It distinguishes itself by focusing on bootstrapping and guidance, contrasting with sibling tools that perform specific actions like trading or staking.

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

Usage Guidelines5/5

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

Description provides clear invocation triggers: when user says 'Start SAP MCP', 'Initialize SAP MCP', 'Load SAP', or asks about capabilities. It also includes execution guidance on pricing, routing, and signer boundary, making it a complete usage guide.

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