Skip to main content
Glama
OOBE-PROTOCOL

SAP MCP Server

Prepare SAP x402 Payment

sap_x402_prepare_payment

Prepare an x402 payment context by setting deposit, price per call, and optional escrow nonce, expiry, and volume curve for agent wallet payments.

Instructions

Prepare an x402 payment context using SDK X402Registry.preparePayment. New production escrow funding should use Escrow V2 fields and nonce-aware flows. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nonceNoOptional escrow nonce as a decimal string. Defaults to 0.
depositNoInitial deposit as a decimal string. Amount in the escrow token smallest unit: lamports for SOL, micro-USDC for USDC, or base units for the configured SPL token.
maxCallsNoOptional maximum number of calls covered
expiresAtNoOptional expiry timestamp in unix seconds
tokenMintNoOptional SPL token mint; omit/null for SOL. Use EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v for mainnet USDC.
agentWalletNoAgent wallet public key (base58)
volumeCurveNoOptional array of { afterCalls, pricePerCall } pricing breakpoints
pricePerCallNoPrice per call as a decimal string. Amount in the escrow token smallest unit: lamports for SOL, micro-USDC for USDC, or base units for the configured SPL token.
tokenDecimalsNoOptional token decimals. Defaults to 6 for USDC/SPL flows when supplied by the SDK and 9 for native SOL.
networkIdentifierNoOptional x402 network identifier written into headers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesMCP content blocks returned to the caller.
isErrorNoTrue when the tool result represents an application-level error.
Behavior4/5

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

Annotations already indicate write operation and non-idempotent. Description adds authorization requirements ('enabled signer mode and MCP policy approval') and hints at SDK interaction, providing context 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?

Description has 4 sentences, front-loaded with the main action, but contains some vague phrases ('SAP MCP context: Payment and settlement flow') that add little value. Not overly long but could be more succinct.

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 (10 parameters, presence of output schema), the description provides reasonable context: overall flow (payment/settlement), prerequisite actions, and authorization needs. Output schema likely explains return values, so this is adequate.

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 description coverage is 100%, so the schema documents all 10 parameters. The description only vaguely references 'nonce-aware flows' but adds no specific parameter details. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it 'Prepare an x402 payment context' using a specific SDK method. It adds domain-specific guidance about new production escrow funding, but does not explicitly differentiate from sibling tools like sap_x402_settle_batch or sap_x402_fetch_escrow.

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?

Provides usage guidance: 'Estimate or fetch state before creating escrows or settling calls' and 'write operations require an enabled signer mode and MCP policy approval.' It implies sequencing but does not directly compare with alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OOBE-PROTOCOL/sap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server