Skip to main content
Glama

Quote the next workflow stage

playground_workflow_quote
Read-only

Quote only the next ready empty steps from workflow_inspect, up to 20 outputs. Does not edit the canvas, prepare approval or submit generation. Safe for the chat workflow form. Returns the exact stageNodeIds, revision and quoteId for a later chat-confirmed playground_workflow_run request.

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>"
    },
    "name": "playground_workflow_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
targetNodeIdsNoWorkflow output node IDs to inspect or produce; dependencies are resolved from the graph.
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 already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description earns credit for adding the side-effect boundary language ('does not edit the canvas, prepare approval or submit generation') that tells the agent the quote is a planning artifact, not a mutation. It also discloses the sequencing requirement (quote first, chat-confirmed run later). It never explains why the operation is non-idempotent despite being read-only — presumably quoteId/expiry semantics — which is a residual gap.

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, front-loaded with what gets quoted and immediately followed by the negative scope and the return contract. Nothing is padded, though dense internal jargon ('ready empty steps', 'chat workflow form') costs some first-read clarity.

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?

Completeness is strong given a full schema, an output schema, and rich annotations: the description still supplies the prerequisite source, the side-effect boundary, the sequencing to playground_workflow_run, and the purpose of the returned quoteId. Remaining gap is placement among the sibling quote tools, which the description does not address.

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 description coverage is 100% and all three parameters are well documented in the schema, including the expectedRevision conflict-recovery instruction. The description adds no parameter-level detail beyond echoing that a revision and stageNodeIds are involved, so the baseline 3 is appropriate. The 'up to 20 outputs' cap in prose also does not map to any declared parameter (targetNodeIds allows 60), which could momentarily confuse an 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?

States a specific operation (quote) on a specific resource (the next ready empty workflow steps sourced from workflow_inspect), with a stated cap of 20 outputs. It also names what it is not: it does not edit the canvas, prepare approval, or submit generation, and it points to playground_workflow_run as the follow-on. An agent can separate it from workflow_inspect and workflow_run without opening a schema.

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?

Gives an implicit prerequisite (the steps come 'from workflow_inspect'), explicit exclusions (no canvas edit, no approval prep, no generation submit), and the sequencing rule that the returned quoteId feeds 'a later chat-confirmed playground_workflow_run request.' It does not say when to prefer this over the sibling quote tools (image/video/media_retry), so it stops short of a full when/when-not map.

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.