Slid Phi Labs

spl_agentic_run

Execute one Agent Commerce Network (ACN) run. Mutating: runs paid and unpaid steps; unpaid steps answer 402 (payment required) instead of running. Requires confirm:true plus demo:true or a Rider + Warrant pair. Use after spl_agentic_plan validates the shape; use spl_agentic_context first when the context is large.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spl_agentic_run"
  }
}

Input Schema

Name	Required	Description
`ops`	No	Ops-feed input for the run.
`pay`	No	True to pay for paid steps when they are reached.
`sku`	No	SKU to buy or price; string id or object.
`url`	No	Target URL for the run.
`cuni`	No	CuNi program or exactness input for the run.
`demo`	No	True to plan or run a demo with no payment and no Rider token.
`host`	No	Target hostname for the run.
`paid`	No	True when payment was already made for this run.
`rail`	No	Payment rail: stripe for humans, x402 for agents.
`swap`	No	Swap details for a cross-chain step (from/to chain, token, amount).
`tool`	No	Tool call spec for the run.
`actor`	No	Actor identity executing the run.
`agent`	No	Agent spec for the run; string id or object.
`audit`	No	Audit or audit-export input; string id or object.
`bytes`	No	Input byte count the run will process; used for the quote.
`chain`	No	Receipt chain for the run; array of prior receipts.
`rider`	No	Agent-Rider JWT identifying the acting agent. Required for live runs unless demo is true.
`action`	No	Run action or stage name, e.g. plan, compress, or a stage key. Determines which stages the plan includes.
`payout`	No	Payout details for the run.
`solana`	No	Solana transaction input for the run.
`confirm`	No	True to execute the run. Required — without it the run is refused.
`dispute`	No	Dispute details for the run.
`mcpTool`	No	MCP tool call spec for the run.
`message`	No	Message payload for an agent-messaging stage.
`sandbox`	No	Sandbox spec for an isolated step.
`warrant`	No	Warrant token authorizing the run's spending. Required for live runs unless demo is true.
`asyncRun`	No	Async run spec for the run.
`crossing`	No	Crossing or bridge identifier when the run moves between systems.
`debridge`	No	deBridge swap input for a cross-chain step.
`x_payment`	No	X-PAYMENT header value for x402 settlement.
`depotStore`	No	Depot store input for the run.
`membership`	No	Membership input for the run.
`reputation`	No	Reputation input for the run; string id or object.
`chamberSeal`	No	Chamber seal input for the run.
`tokenBudget`	No	Token budget for the run; string id or object.
`depotBilling`	No	Depot billing input for the run.
`depotReceipt`	No	Depot receipt input for the run.
`privateBench`	No	Private benchmark input for the run.
`conductorTask`	No	Conductor task spec; string id or object.
`riderPaidCall`	No	Paid Rider call input for the run.
`standingRider`	No	Standing Rider credential for the run; string id or object.
`parent_receipt`	No	Parent receipt id when this run continues another run.
`conductorReview`	No	Conductor review input for the run.
`delegation_mode`	No	Delegation mode for the run.
`warrantTemplate`	No	Warrant template to apply to the run; string id or object.

Schema Changelog

Changes observed during successful MCP inspections.

Changed45 schema fields changedNov 7, 2026

addedInput schema / properties / action / description

Added value: +"Run action or stage name, e.g. plan, compress, or a stage key. Determines which stages the plan includes."

addedInput schema / properties / actor / description

Added value: +"Actor identity executing the run."

addedInput schema / properties / agent / description

Added value: +"Agent spec for the run; string id or object."

addedInput schema / properties / asyncRun / description
```
Added value: +"Async run spec for the run."
```

addedInput schema / properties / audit / description

Added value: +"Audit or audit-export input; string id or object."

addedInput schema / properties / bytes / description

Added value: +"Input byte count the run will process; used for the quote."

addedInput schema / properties / chain / description

Added value: +"Receipt chain for the run; array of prior receipts."

addedInput schema / properties / chamberSeal / description
```
Added value: +"Chamber seal input for the run."
```
addedInput schema / properties / conductorReview / description
```
Added value: +"Conductor review input for the run."
```

addedInput schema / properties / conductorTask / description

Added value: +"Conductor task spec; string id or object."

addedInput schema / properties / confirm / description

Added value: +"True to execute the run. Required — without it the run is refused."

addedInput schema / properties / crossing / description

Added value: +"Crossing or bridge identifier when the run moves between systems."

addedInput schema / properties / cuni / description

Added value: +"CuNi program or exactness input for the run."

addedInput schema / properties / debridge / description

Added value: +"deBridge swap input for a cross-chain step."

addedInput schema / properties / delegation_mode / description
```
Added value: +"Delegation mode for the run."
```

addedInput schema / properties / demo / description

Added value: +"True to plan or run a demo with no payment and no Rider token."

addedInput schema / properties / depotBilling / description
```
Added value: +"Depot billing input for the run."
```
addedInput schema / properties / depotReceipt / description
```
Added value: +"Depot receipt input for the run."
```
addedInput schema / properties / depotStore / description
```
Added value: +"Depot store input for the run."
```
addedInput schema / properties / dispute / description
```
Added value: +"Dispute details for the run."
```
addedInput schema / properties / host / description
```
Added value: +"Target hostname for the run."
```
addedInput schema / properties / mcpTool / description
```
Added value: +"MCP tool call spec for the run."
```
addedInput schema / properties / membership / description
```
Added value: +"Membership input for the run."
```

addedInput schema / properties / message / description

Added value: +"Message payload for an agent-messaging stage."

addedInput schema / properties / ops / description
```
Added value: +"Ops-feed input for the run."
```

addedInput schema / properties / paid / description

Added value: +"True when payment was already made for this run."

addedInput schema / properties / parent_receipt / description

Added value: +"Parent receipt id when this run continues another run."

addedInput schema / properties / pay / description

Added value: +"True to pay for paid steps when they are reached."

addedInput schema / properties / payout / description
```
Added value: +"Payout details for the run."
```
addedInput schema / properties / privateBench / description
```
Added value: +"Private benchmark input for the run."
```

addedInput schema / properties / rail / description

Added value: +"Payment rail: stripe for humans, x402 for agents."

addedInput schema / properties / reputation / description

Added value: +"Reputation input for the run; string id or object."

addedInput schema / properties / rider / description

Added value: +"Agent-Rider JWT identifying the acting agent. Required for live runs unless demo is true."

addedInput schema / properties / riderPaidCall / description
```
Added value: +"Paid Rider call input for the run."
```
addedInput schema / properties / sandbox / description
```
Added value: +"Sandbox spec for an isolated step."
```

addedInput schema / properties / sku / description

Added value: +"SKU to buy or price; string id or object."

addedInput schema / properties / solana / description

Added value: +"Solana transaction input for the run."

addedInput schema / properties / standingRider / description

Added value: +"Standing Rider credential for the run; string id or object."

addedInput schema / properties / swap / description

Added value: +"Swap details for a cross-chain step (from/to chain, token, amount)."

addedInput schema / properties / tokenBudget / description

Added value: +"Token budget for the run; string id or object."

addedInput schema / properties / tool / description
```
Added value: +"Tool call spec for the run."
```
addedInput schema / properties / url / description
```
Added value: +"Target URL for the run."
```

addedInput schema / properties / warrant / description

Added value: +"Warrant token authorizing the run's spending. Required for live runs unless demo is true."

addedInput schema / properties / warrantTemplate / description

Added value: +"Warrant template to apply to the run; string id or object."

addedInput schema / properties / x_payment / description

Added value: +"X-PAYMENT header value for x402 settlement."

Changed4 schema fields changedNov 6, 2026
- addedInput schema / properties / chamberSeal
```
Added value: +{
+  "type": "object"
+}
```
- addedInput schema / properties / depotStore
```
Added value: +{
+  "type": "object"
+}
```
- addedInput schema / properties / membership
```
Added value: +{
+  "type": "object"
+}
```
- addedInput schema / properties / riderPaidCall
```
Added value: +{
+  "type": "object"
+}
```
Changed1 schema field changedNov 6, 2026
- addedInput schema / properties / tokenBudget
```
Added value: +{
+  "type": "object"
+}
```

Changed20 schema fields changedNov 5, 2026

addedInput schema / properties / agent

Added value: +{
+  "type": [
+    "string",
+    "object"
+  ]
+}

addedInput schema / properties / asyncRun
```
Added value: +{
+  "type": "object"
+}
```

addedInput schema / properties / audit

Added value: +{
+  "type": [
+    "string",
+    "object"
+  ]
+}

addedInput schema / properties / conductorReview
```
Added value: +{
+  "type": "object"
+}
```

addedInput schema / properties / conductorTask

Added value: +{
+  "type": [
+    "string",
+    "object"
+  ]
+}

addedInput schema / properties / depotBilling
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / depotReceipt
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / dispute
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / mcpTool
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / message
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / ops
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / payout
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / privateBench
```
Added value: +{
+  "type": "object"
+}
```

addedInput schema / properties / reputation

Added value: +{
+  "type": [
+    "string",
+    "object"
+  ]
+}

addedInput schema / properties / sandbox
```
Added value: +{
+  "type": "object"
+}
```

addedInput schema / properties / sku

Added value: +{
+  "type": [
+    "string",
+    "object"
+  ]
+}

addedInput schema / properties / solana
```
Added value: +{
+  "type": "object"
+}
```

addedInput schema / properties / standingRider

Added value: +{
+  "type": [
+    "string",
+    "object"
+  ]
+}

addedInput schema / properties / tool
```
Added value: +{
+  "type": "object"
+}
```

addedInput schema / properties / warrantTemplate

Added value: +{
+  "type": [
+    "string",
+    "object"
+  ]
+}

AddedNov 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, destructive=false, but the description adds what those hints cannot: unpaid steps answer 402 rather than executing, and a run is refused without confirm plus either demo:true or a Rider/Warrant pair. It stops short of saying what a successful run returns or how partial failure is reported, so it falls just short of a 5.

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?

Three tight sentences with the mutation/payment warning front-loaded ahead of prerequisites and ordering guidance. Density is high but nothing is padding; the middle sentence is slightly compressed in a way that requires a second read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 45-parameter, non-idempotent, open-world tool with no output schema, the description covers gating (confirm/demo/rider/warrant) and payment behavior but never says what a run produces (receipts? a receipt chain?) or how the many domain inputs relate to the action value. Adequate to call it correctly, incomplete to predict its results.

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?

Schema coverage is 100%, so the baseline is 3; the description earns more by stating the cross-parameter constraint (confirm:true combined with demo:true or Rider + Warrant) that no single per-property schema description can express. It says nothing about the long tail of domain parameters (swap, debridge, conductorTask, chamberSeal), which the schema must carry alone.

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+resource: "Execute one Agent Commerce Network (ACN) run." That is unambiguous and clearly separates this tool from read/lookup siblings such as spl_agentic_plan, spl_agentic_context, and the various *_get/*_search tools.

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

Usage Guidelines5/5

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

It gives explicit sequencing: "Use after spl_agentic_plan validates the shape; use spl_agentic_context first when the context is large." Both alternatives and the conditions that select them are named, and the demo-vs-live path (confirm + demo, or Rider + Warrant) is spelled out.

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

All Slid Phi Labs 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.

Resources

Need Help?