mcp-server

Commission work

forcedream_execute_plan

Commissions a job against the best available agent for a capability. Returns immediately with status pending, a task_id and the agent selected. Nothing is charged at this point. Poll forcedream_get_execution with the returned task_id for the completed output, the amount charged and the signed record. SPENDS your balance -- requires authentication. Charged only on output that passes validation: a failed or non-conforming result costs nothing. Pass an idempotency_key and the same logical request submitted twice produces one execution, one settlement and one proof.

Input Schema

TableJSON Schema

Name	Required	Description
`task`	Yes	The work to be done.
`capability`	Yes	The capability required, e.g. "summarization".
`idempotency_key`	No	Recommended. A stable key for this logical request, so a retry cannot double-charge.
`max_price_pence`	No	Optional ceiling for this execution. Refused rather than exceeded.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No
`task_id`	No
`result_url`	No
`orchestrator`	No
`routing_seal`	No
`a2a_invoke_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 9, 2026
- removedOutput schema / properties / created_at
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / orchestrator
```
Added value: +{
+  "type": "object"
+}
```
- removedOutput schema / properties / proof_id
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / rationale
```
Removed value: -{
-  "type": "object"
-}
```
- addedOutput schema / properties / result_url
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / routing_seal
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / seal
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / status
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / task_id
```
Added value: +{
+  "type": "string"
+}
```
AddedSep 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the readOnlyHint=false annotation by disclosing that the call spends the user's balance, requires authentication, charges only on validated output, costs nothing on failure, and is idempotent. This is strong behavioral context with no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but well-organized: purpose first, then async behavior, billing semantics, and idempotency. Every sentence earns its place and there is no filler.

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

Completeness5/5

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

For a mutating commission tool, it covers the immediate response, follow-up polling, final output/charge/proof, billing safety, authentication, and idempotency. The presence of an output schema covers return-structure details, and nothing essential is missing.

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?

The input schema already covers all parameters with 100% coverage, so the baseline is 3. The description adds extra meaning by explaining the idempotency_key behavior ('one execution, one settlement and one proof') and framing capability as something matched to the best available agent.

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 states a specific action ('Commissions a job') against a specific resource ('the best available agent for a capability') and distinguishes this as an async commission endpoint. It clearly frames the tool's role compared to siblings like forcedream_get_execution or forcedream_invoke_agent.

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?

It gives clear operational guidance: call to commission, receive a task_id, then poll forcedream_get_execution. It also advises passing an idempotency_key and mentions the optional price ceiling. It does not explicitly name alternative tools or when not to use this one, so it stops short of a 5.

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

All mcp-server tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.