SAP MCP Server

Openbook Place Order

openbook_placeOrder

Place an order on an Openbook market. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry.

SAP MCP execution guidance: Intent: SAP MCP tool 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
`side`	Yes	Side parameter for Openbook Place Order.
`size`	Yes	Raw token amount (smallest unit)
`price`	Yes	Price parameter for Openbook Place Order.
`wallet`	Yes	Solana public key (base58)
`marketId`	Yes	Solana public key (base58)
`orderType`	No	Order Type parameter for Openbook Place Order.

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: +"Openbook Place Order input schema. Intent: SAP MCP tool 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

C2.9/5.0

Behavior3/5

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

Annotations indicate a non-read-only, non-destructive write operation. The description adds some behavioral context via the 'Signer boundary' note: hosted builders never receive keypair bytes and value-moving results must be finalized locally. This is useful transparency for execution. However, it lacks details on failure modes, partial fills, or cancellation behavior. The generic SAP MCP boilerplate partially addresses the execution model but is not focused on this tool's specifics.

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?

Only the first sentence is tool-specific; the remainder is a generic SAP MCP workflow block that is likely repeated across many tools. This verbosity and repetition harms conciseness. The structure buries the core purpose inside irrelevant context.

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 tool has 6 parameters (5 required) and an output schema, but the description does not explain the return value, error behavior, or how to interpret the result. The SAP MCP notes about signing imply the output may be a transaction to be signed, but this is not explicit. Missing context like slippage, expiry, or market validation leaves the agent underinformed for correct invocation.

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% with descriptions for all 6 parameters. The description adds no additional semantic meaning beyond the schema (e.g., how price and size interact, or the meaning of 'orderType'). With high schema coverage, the baseline score is 3; the description does not improve it.

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 initial sentence 'Place an order on an Openbook market' clearly states the verb and resource. The name and title match. However, the description is cluttered with generic SAP MCP context that does not enhance purpose clarity. It distinguishes from siblings like openbook_cancelOrder only implicitly via the name, missing an explicit distinction.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., limit vs. IOC vs. postOnly order types). The description lacks instructions on prerequisites, order lifecycle, or success criteria. The SAP MCP guidance about pricing and routing is generic and does not help with trading-specific usage decisions.

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.