SAP MCP Server

Fetch SAP Escrow V2

sap_fetch_escrow_v2

Read-onlyIdempotent

Fetch a V2 escrow by escrow PDA, or by agent PDA, depositor, and nonce. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.

SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. 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	Escrow nonce (default: 0) — used with agentPda and depositor
`agentPda`	No	Agent PDA (base58) — used when escrowPda is omitted
`depositor`	No	Optional depositor wallet (base58) to filter by
`escrowPda`	No	Escrow V2 PDA (base58) to fetch directly

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: +"Fetch SAP Escrow V2 input schema. Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. 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."

First observedJul 13, 2026

TDQS

A4/5.0

Behavior4/5

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

The description adds value beyond annotations by stating it is a read-only SDK wrapper, paid read-premium, and hosted read with signer boundary info. Annotations already declare readOnlyHint=true, so no contradiction; the description enriches with pricing and routing context.

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 core purpose but includes repetitive execution guidance (e.g., 'estimate first' mentioned twice). The context and guidance paragraphs are verbose and could be streamlined without losing information.

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?

The description covers the fetch functionality, read-only nature, and provides execution guidance for pricing/routing. With a present output schema and clear annotations, it is fairly complete. Missing comparison to V1 escrow or return format details, but these are not critical for a read-only fetch tool.

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?

Input schema covers all 4 parameters with descriptions (100% coverage). The tool description does not add new semantic details for individual parameters but does clarify the two lookup modes (by escrowPda vs by agentPda+depositor+nonce). 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 tool fetches a V2 escrow by either escrow PDA or by agent PDA, depositor, and nonce. This specific verb-resource combination distinguishes it from sibling fetch tools like sap_fetch_escrow (V1) and other fetch operations.

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 advises using reads to inspect chain state before mutations, providing clear context. However, it does not explicitly contrast with alternatives (e.g., when to use sap_fetch_escrow_v2 vs sap_fetch_escrow), and the execution guidance is more about pricing/routing than comparative usage.

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.