Skip to main content
Glama

Inspect workflow inputs and execution stages

playground_workflow_inspect
Read-onlyIdempotent

Read typed source input contracts, generation dependencies, completed outputs, pending/active work and blockers. Returns the next ready stage without spending. Use before running a saved campaign. Returns typed editable inputs, dependencies, stages and workflow readiness.

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

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.

Output Schema

NameRequiredDescriptionDefault
nextYesSuggested next action; it does not authorize spending.
stepsYes
inputsYes
statusYes
revisionYes
workflowYes
canvasUrlYes
executionYes
projectIdYes
readyNodeIdsYes
lockedNodeIdsYes
completedNodeIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description's real addition is 'without spending', which tells the agent this inspection incurs no cost — useful context that annotations do not carry. It adds nothing about page sizes, size limits, or what a blocked readiness state looks like.

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

Conciseness3/5

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

The description is front-loaded with the resource list and the key precondition, which is good. However, 'Returns the next ready stage' and 'Returns typed editable inputs, dependencies, stages and workflow readiness' are redundant return-value sentences, especially since an output schema already exists.

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 two-parameter read-only tool with full schema coverage, annotations, and an output schema, the description covers purpose and the cost-free precondition adequately. Credit is reduced because two sentences are spent restating return values that the output schema already defines, while behavior around blocked stages or large graphs is left unaddressed.

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%, so projectId provenance and targetNodeIds graph-dependency resolution are already documented. The description mentions 'dependencies' and 'typed inputs' but adds no syntax, format, or constraint detail beyond the schema, so baseline 3 applies.

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 first sentence names specific resources: typed input contracts, generation dependencies, completed outputs, pending work, blockers, and the next ready stage. This is a clear read/inspect verb plus concrete scope, and 'returns the next ready stage' distinguishes it from workflow_run. It does not explicitly name a sibling, so no 5.

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?

'Use before running a saved campaign' gives a clear precondition that effectively routes to the run tool, and 'without spending' tells an agent this is the safe check step. No when-not-to-use or named alternative is given, and 'campaign' does not match the 'workflow' naming used elsewhere, which weakens it slightly.

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.