SAP MCP Server

Plan SAP Runtime Repair

sap_runtime_repair_plan

Read-onlyIdempotent

Free helper that returns the pinned latest-release repair command for hosted SAP MCP plus local sap_payments bridge setup. Use this before asking users to manually edit runtime config.

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

Name	Required	Description	Default
`agent`	No	Optional runtime to focus repair instructions on.

Output Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	Plan type.
`package`	Yes	Pinned npm package spec.
`success`	Yes	Whether the repair plan was generated.
`commands`	Yes	OS-specific repair command aliases.
`serverMode`	Yes	Current server mode.
`latestVersion`	Yes	Pinned SAP MCP package version for repair.
`repairCommand`	Yes	Primary local command to repair hosted MCP and sap_payments bridge config.
`targetRuntime`	Yes	Runtime selected for repair guidance.
`wizardCommand`	Yes	Full local wizard command for profile creation or full setup.
`hostedEndpoint`	Yes	Hosted SAP MCP endpoint.
`whatRepairDoes`	Yes	Concrete operations performed by repair.
`agentInstructions`	Yes	Instructions agents should follow without guessing.
`expectedAfterRestart`	Yes	Tool namespaces and bridge tools expected after restarting the runtime.

TDQS

A4/5.0

Behavior4/5

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

Aligns with annotations (readOnlyHint, idempotentHint, destructiveHint) and adds useful context about being free, the signer boundary, and routing. The boilerplate guidance on execution provides additional behavioral transparency beyond annotations.

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 core description is concise, but the additional boilerplate 'SAP MCP execution guidance' block is lengthy and generic, reducing conciseness. The key information is front-loaded, but extra text could be trimmed.

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 simplicity (one optional parameter, output schema exists), the description covers the tool's purpose, usage, and behavioral nuances. The guidance on pricing and routing adds necessary context for an agent invoking it, making it fairly complete.

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?

The only parameter 'agent' is described as 'Optional runtime to focus repair instructions on' in the description, adding clarity to its purpose beyond the enum values. With 100% schema coverage (object-level description present), this is adequate but not exceptional.

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 it returns a repair command for SAP MCP runtime and local payment bridge setup. It uses a specific verb ('returns') and resource ('repair command'), and the unique function distinguishes it from 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?

Explicitly advises to use before manual runtime config editing, providing clear context. However, it does not explicitly mention when not to use or offer alternatives, though the unique purpose inherently provides such guidance.

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.

Plan SAP Runtime Repair

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources