SAP MCP Server

Settle SAP x402 Calls

sap_x402_settle

Destructive

Settle served x402 calls through SDK X402Registry.settle. Must be called by the agent owner wallet. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.

SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. 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
`nonce`	No	Optional escrow nonce as a decimal string. Defaults to 0.
`commitment`	No	Optional processed\|confirmed\|finalized commitment
`maxRetries`	No	Optional RPC retry limit
`serviceData`	No	Service data to hash into the settlement proof
`computeUnits`	No	Optional compute-unit limit
`callsToSettle`	No	Number of calls to settle
`skipPreflight`	No	Optional skip preflight flag
`depositorWallet`	No	Depositor wallet public key (base58)
`priorityFeeMicroLamports`	No	Optional priority fee in microlamports per compute unit

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 24, 2026

addedInput schema / description

Added value: +"Settle SAP x402 Calls input schema. Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. 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. Use exact field names from this schema; do not guess aliases or include private key material."

Changed1 schema field changedJul 17, 2026

addedInput schema / properties / nonce

Added value: +{
+  "description": "Optional escrow nonce as a decimal string. Defaults to 0.",
+  "type": "string"
+}

First observedJul 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the annotations indicating a destructive write operation, the description adds context about authorization (owner wallet, signer mode, MCP policy approval) and the need to preview cost and effects. No contradiction 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?

The description is front-loaded with the purpose, but includes repetitive SAP MCP boilerplate that adds length. Nevertheless, it is structured and most sentences contribute meaningful guidance.

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 complexity of settlement and the presence of an output schema, the description covers caller requirements, sequencing (estimate first), and routing options. Lacks details on expected output, but output schema handles that.

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?

All 9 parameters have descriptions in the input schema (100% coverage). The description adds only a general note about using exact field names, but no additional per-parameter semantics. Baseline of 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?

The description clearly states the verb 'Settle' and the resource 'served x402 calls', referencing the specific SDK method 'X402Registry.settle'. This distinguishes it from siblings like sap_x402_settle_batch.

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 caller requirements ('Must be called by the agent owner wallet'), prerequisites ('Estimate or fetch state before...'), and provides guidance on cost estimation and routing alternatives. However, it does not explicitly differentiate from the sibling sap_x402_settle_batch.

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.