SAP MCP Server

sap phoenix build place limit order

sap_phoenix_build_place_limit_order

Build an unsigned Phoenix limit order transaction. Pass authority, symbol, side, priceUsd (human limit price, e.g. "106.50"), baseUnits (human size). Raw priceInTicks/numBaseLots also accepted. Returns transactionBase64 for browser approval. Builder fee applies.

SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. 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	Order side: bid (buy) or ask (sell)
`size`	No	Alias of baseUnits
`price`	No	Alias of priceUsd
`symbol`	Yes	Market symbol (e.g. SOL)
`priceUsd`	No	Human limit price in USD (e.g. "106.50")
`authority`	Yes	Trader authority public key (base58)
`baseUnits`	No	Human size in base units (e.g. "0.01")
`holderTier`	No	Caller $STEVE holder tier — lowers the builder fee (bronze −10%, silver −20%, gold −30%, platinum −50%). Omit for the standard fee.
`limitPrice`	No	Alias of priceUsd
`reduceOnly`	No	Reduce-only: order can only decrease an existing position (OrderFlags.ReduceOnly)
`numBaseLots`	No	Raw base lots (overrides baseUnits)
`priceInTicks`	No	Limit price in ticks (raw integer; overrides priceUsd)
`clientOrderId`	No	Client order ID (unique per trader); optional
`traderPdaIndex`	No	Trader PDA Index parameter for sap phoenix build place limit order.
`traderSubaccountIndex`	No	Trader Subaccount Index parameter for sap phoenix build place limit 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 changedSep 6, 2026

addedInput schema / properties / holderTier

Added value: +{
+  "description": "Caller $STEVE holder tier — lowers the builder fee (bronze −10%, silver −20%, gold −30%, platinum −50%). Omit for the standard fee.",
+  "enum": [
+    "bronze",
+    "silver",
+    "gold",
+    "platinum"
+  ],
+  "type": "string"
+}

Changed1 schema field changedSep 6, 2026

addedInput schema / properties / reduceOnly

Added value: +{
+  "description": "Reduce-only: order can only decrease an existing position (OrderFlags.ReduceOnly)",
+  "type": "boolean"
+}

Changed9 schema fields changedSep 6, 2026

addedInput schema / properties / baseUnits

Added value: +{
+  "description": "Human size in base units (e.g. \"0.01\")",
+  "type": "string"
+}

changedInput schema / properties / clientOrderId / description

Previous value: -"Client order ID (unique per trader)"New value: +"Client order ID (unique per trader); optional"

addedInput schema / properties / limitPrice

Added value: +{
+  "description": "Alias of priceUsd",
+  "type": "string"
+}

changedInput schema / properties / numBaseLots / description

Previous value: -"Number of base lots"New value: +"Raw base lots (overrides baseUnits)"

addedInput schema / properties / price

Added value: +{
+  "description": "Alias of priceUsd",
+  "type": "string"
+}

changedInput schema / properties / priceInTicks / description

Previous value: -"Limit price in ticks (raw integer)"New value: +"Limit price in ticks (raw integer; overrides priceUsd)"

addedInput schema / properties / priceUsd

Added value: +{
+  "description": "Human limit price in USD (e.g. \"106.50\")",
+  "type": "string"
+}

addedInput schema / properties / size

Added value: +{
+  "description": "Alias of baseUnits",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "authority",
-  "symbol",
-  "side",
-  "priceInTicks",
-  "numBaseLots",
-  "clientOrderId"
-]New value: +[
+  "authority",
+  "symbol",
+  "side"
+]

AddedSep 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

It discloses that the tool returns a transactionBase64 for browser approval, that a builder fee applies, and that hosted builders never receive keypair bytes while value-moving results must be finalized locally. This is meaningful context beyond annotations and matches the non-readOnly, non-idempotent flags.

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 core action and key inputs, followed by a structured execution-guidance block. It is a bit dense and repeats guidance that also appears in the schema description, but each sentence in the tool description carries operational value.

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?

For a 15-parameter builder with an output schema, the description covers the essential call pattern, return value, fee behavior, and signer boundary. It does not explicitly state that one price and one size input (human or raw) are effectively required, which is a minor gap given the schema only marks three fields as required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage the baseline is 3, but the description adds value by clarifying human vs raw inputs ('priceUsd (human limit price, e.g. "106.50")') and noting raw priceInTicks/numBaseLots are accepted. It does not repeat every parameter, relying on the schema for the rest, which 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 opens with a specific verb and resource: 'Build an unsigned Phoenix limit order transaction.' It clearly distinguishes this builder from market/conditional/stop-order siblings by naming limit order and the returned artifact. The examples for price and size make the purpose unambiguous.

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 gives clear execution context: a hosted unsigned transaction builder that must be priced first, paid, and finalized locally when signing is required. It does not explicitly contrast this tool with market/conditional order builders, but the intent and routing guidance (sap_estimate_tool_cost, sap_payments_call_paid_tool) effectively tell an agent how to proceed.

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.