SAP MCP Server

Install SAP MCP Skills

sap_skills_install

Install bundled SAP MCP skills into a local agent skill directory. Requires confirm: true.

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
`agent`	No	Agent parameter for Install SAP MCP Skills.
`skills`	No	Skills parameter for Install SAP MCP Skills.
`confirm`	No	Confirm flag required before local signing, payment, or write execution. Set true only after the user approves the preview/cost.
`targetDir`	No	Target Dir parameter for Install SAP MCP Skills.

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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 28, 2026

changedInput schema / properties / agent / enum

Previous value: -[
-  "claude",
-  "codex",
-  "hermes",
-  "openclaw",
-  "custom"
-]New value: +[
+  "claude",
+  "codex",
+  "hermes",
+  "openclaw",
+  "clawpump",
+  "custom"
+]

Changed2 schema fields changedJul 24, 2026

addedInput schema / description

Added value: +"Install SAP MCP Skills input schema. 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. Use exact field names from this schema; do not guess aliases or include private key material."

changedInput schema / properties / confirm / description

Previous value: -"Confirm confirmation flag required before Install SAP MCP Skills performs a local write."New value: +"Confirm flag required before local signing, payment, or write execution. Set true only after the user approves the preview/cost."

First observedJul 13, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The description goes beyond annotations by stating that confirmation is required (confirm: true) and providing execution context (pricing, routing, signer boundary). The annotations (readOnlyHint=false) are consistent with a write operation. The additional guidance adds value.

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

Conciseness2/5

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

The description is brief but includes a large block of generic execution guidance that is not specific to this tool, reducing conciseness. The core installation purpose is stated in the first sentence, but the boilerplate could be trimmed.

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

Completeness2/5

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

The description does not explain what happens after installation, what the output looks like, or how to use the installed skills. Given that an output schema exists, the description could still benefit from summarizing the outcome (e.g., list of installed skills).

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% and parameter descriptions are provided, albeit minimal. The tool description does not add further meaning beyond what the schema provides, so it meets the baseline expectation.

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 verb (install) and resource (bundled SAP MCP skills) and specifies the target location (local agent skill directory). It distinguishes from sibling tools like sap_skills_list or sap_skills_bundle by focusing on installation.

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

Usage Guidelines3/5

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

The description mentions 'Requires confirm: true' and provides high-level guidance on intent (agent bootstrap, routing, skills, or repair guidance) and pricing. However, it does not explicitly state when to use this tool over alternatives or provide exclusion criteria.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.