Skip to main content
Glama
kuklaph
by kuklaph

Perform Workflow Transition

cascade_perform_workflow_transition

Advance an active workflow to its next step by executing a named action like approve or reject. Requires workflow ID and action identifier from prior workflow information call.

Instructions

Advance an in-flight workflow to its next step (approve, reject, publish, etc.).

Executes a named action against an active workflow. The workflowId and actionIdentifier come from a prior cascade_read_workflow_information call — the tool does not enumerate actions itself. A transitionComment is recommended so reviewers understand the decision; it's stored in the workflow history. Once the final step is executed, Cascade may publish, delete, or otherwise commit the change associated with the workflow.

Args:

  • workflowId (string, required): The active workflow's id (from cascade_read_workflow_information)

  • actionIdentifier (string, required): The action to take (from workflow.actions[].identifier)

  • transitionComment (string, optional): User comment explaining this transition

Returns: Cascade OperationResult: { success: true } On failure: { success: false, message: "" }

Examples:

  • Use when: "Approve an editor's page submission" -> { workflowId: "...", actionIdentifier: "approve", transitionComment: "Looks good." }

  • Use when: "Reject and send back" -> { workflowId: "...", actionIdentifier: "reject", transitionComment: "Fix the headline." }

  • Don't use when: You don't yet know which actions are valid — call cascade_read_workflow_information first.

  • Don't use when: No workflow exists — this only advances an in-flight one.

Error Handling:

  • "Workflow not found" when workflowId is invalid or already finished

  • "Invalid action" when actionIdentifier is not among the workflow's available actions

  • "Permission denied" when current user can't act on this workflow step. Responses are JSON text; structuredContent is authoritative when the response fits. Oversized responses return bounded _cache metadata for cascade_read_response. For cascade_read, read_mode controls preview versus raw Cascade payload shape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdNoREQUIRED: The ID of the active workflow to transition.
actionIdentifierNoREQUIRED: The identifier of the workflow action/transition to perform (e.g., 'approve', 'reject').
transitionCommentNoOptional comment recorded with the workflow transition.
Behavior4/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description adds behavioral context: it executes a named action, may trigger publishing/deletion upon final step, stores comments in history, and provides error scenarios. No contradiction with annotations.

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?

The description is well-organized with labeled sections (Args, Returns, Examples, Error Handling). It is somewhat lengthy but each sentence adds value. Could be slightly more concise but remains clear and focused.

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 no output schema, the description thoroughly explains the return format and error messages. It covers prerequisites, side effects, and error handling, making it complete for a workflow transition tool with good annotations.

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 describes each parameter briefly. The description adds meaningful context: workflowId comes from a prior call, actionIdentifier from workflow.actions[].identifier, and transitionComment is recommended for reviewers. This enhances schema coverage of 100%.

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 clearly states it advances an in-flight workflow to its next step (approve, reject, publish, etc.), with a specific verb and resource. It distinguishes itself from siblings by explicitly referencing the prerequisite tool cascade_read_workflow_information and by contrasting with read-only 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?

The description provides explicit when-to-use and when-not-to-use guidance, including examples (approve, reject) and negative conditions ('Don't use when: You don't yet know which actions are valid...', 'Don't use when: No workflow exists'). It also explains prerequisite calls.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kuklaph/cascade-cms-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server