Skip to main content
Glama

Quote or prepare a ready workflow stage

playground_workflow_run
Destructive

Run a saved workflow through its ready image/video/audio stages. quote:true prices up to 20 ready nodes including connected List batches. Pass the returned stageNodeIds, expectedRevision, quoteId and a NEW idempotencyKey with quote:false to prepare chat confirmation. Does not auto-approve or dispatch dependent stages. After existing jobs settle, inspect/quote the next stage until completed. Preserve completed, active and uncertain work; no Berrys-agent delegation is needed. Returns a stage quote or execution/approval result with run and job tracking information.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "expectedRevision": "<expectedRevision>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "playground_workflow_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteNoWhen true, return pricing without executing paid generation; show the quote and obtain user approval before spending.
quoteIdNoExact quote ID returned by preparation or quoting; submit it with the unchanged quoted request.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
stageNodeIdsNoReady-stage node IDs returned by the workflow quote for this execution.
targetNodeIdsNoWorkflow output node IDs to inspect or produce; dependencies are resolved from the graph.
idempotencyKeyYesUnique key for this request; reuse only when retrying the identical request after a lost response. Use a new key after quoting or changing inputs.
expectedRevisionYesCurrent canvas revision from canvas_read; on revision_conflict, read again and rebuild the change.

Output Schema

NameRequiredDescriptionDefault
nextNoSuggested next action; it does not authorize spending.
errorNo
itemsNo
nodesNo
runIdNo
stepsNo
inputsNo
reasonNo
reviewNo
statusYes
balanceNo
creditsNo
nodeIdsNo
quoteIdNo
replayedNo
revisionNo
workflowNo
canvasUrlNo
executionNo
expiresAtNoSerialized ISO timestamp.
projectIdNo
dispatchIdsNo
confirmationNo
readyNodeIdsNo
stageNodeIdsNo
totalCreditsNo
workflowNextNo
failedNodeIdsNo
lockedNodeIdsNo
validitySecondsNo
approvalLocationNo
completedNodeIdsNo
expectedRevisionNo
inputFingerprintNo
uncertainNodeIdsNo
sufficientCreditsNo
estimatedBalanceAfterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare destructive/openWorld/non-idempotent, but the description adds real behavioral context: quoting does not execute paid generation, a NEW idempotencyKey is required after quoting or changing inputs, dependent stages are not dispatched, and completed/active/uncertain work must be preserved. The 'no Berrys-agent delegation is needed' clause is opaque and adds little. It stops short of stating permission or concurrency constraints, but overall this exceeds the annotation baseline.

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?

Front-loaded with the core action and the quote/prepare contract, then the ordering rules, with no filler around them. The prose is telegraphic and one clause ('no Berrys-agent delegation is needed') is unclear rather than economical, which keeps it off a 5.

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?

Given an output schema covers the return values and a fully described 7-parameter schema, the description supplies what's still missing: the quote-then-prepare state machine, the stage iteration loop, and the non-dispatch/preservation guarantees. Nothing an agent needs to avoid an incorrect spend or a stale-revision failure is absent.

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, but the description adds cross-parameter meaning the schema can't: stageNodeIds, expectedRevision, and quoteId must be the values returned by the quote call, paired with a fresh idempotencyKey and quote:false. It also notes the up-to-20 ready node limit including connected List batches, which complements the maxItems constraint.

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 description states a specific verb and resource ('Run a saved workflow through its ready image/video/audio stages') and clarifies the dual quote/prepare mode with 'quote:true prices ... with quote:false to prepare chat confirmation.' It is clear about scope, but never names or distinguishes itself from the close sibling playground_workflow_quote, leaving the agent to infer the split.

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 concrete sequencing guidance: quote first, then pass the returned identifiers with quote:false, obtain user approval, and after existing jobs settle inspect/quote the next stage until completed. It also states what it does not do ('Does not auto-approve or dispatch dependent stages'). What it lacks is explicit routing against alternatives such as playground_workflow_quote or playground_node_run.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.