Skip to main content
Glama
Sign In
OmniFlow MCP

OmniFlow MCP

by DanikVR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

flow_cancel

Cancel queued generations that haven't started yet, while allowing already-running video clips to continue.

Instructions

Remove everything that has not started generating yet. Clips already in progress are not interrupted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flow_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the disclosure burden. It clearly discloses the key behavioral trait: pending items are removed, but already-started clips continue. It does not mention reversibility or response behavior, but the core side effect is transparent.

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 two short sentences with no filler. The main action is front-loaded, and the boundary condition is stated immediately after.

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?

For a zero-parameter cancellation tool with no output schema, the description is sufficiently complete to invoke correctly. It explains what will be removed and what will be preserved, leaving little ambiguity for the agent.

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 has zero parameters and complete schema coverage, so there is nothing for the description to add about parameter meaning. With 0 params, this is a solid baseline.

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 verb ('Remove') and a clear resource/scope ('everything that has not started generating yet'), and explicitly distinguishes what is affected from what is not. This makes its purpose distinct from siblings like flow_generate, flow_status, and flow_edit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool: when you want to cancel generation tasks that have not started. However, it does not explicitly name alternatives or state when not to use it beyond noting that in-progress clips are not interrupted.

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

Deploy Server

Other Tools