Skip to main content
Glama
Sign In
EasySourceFlow

EasySourceFlow

by john-ops-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

easysourceflow_cancel_job

Destructive

Cancel a queued or running job to prevent it from overwriting outputs, while allowing background subprocesses to finish.

Instructions

Cancel a queued or running EasySourceFlow job. Running subprocess work may finish in the background, but the canceled job will not be overwritten.

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": {
      "job_id": "<job_id>"
    },
    "name": "easysourceflow_cancel_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesExisting job ID to cancel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The description adds valuable context beyond annotations by noting that 'running subprocess work may finish in the background, but the canceled job will not be overwritten.' This informs the agent of side effects even though destructiveHint is true.

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?

Two concise sentences, front-loaded with the primary action and key nuance. Every word earns its place.

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?

For a simple cancel tool with one parameter and annotations present, the description is fully adequate. It covers the cancellation behavior and subprocess implications without needing output schema details.

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?

With 100% schema coverage, the description of job_id ('Existing job ID to cancel.') adds no additional meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 specifies the action ('Cancel') and the resource ('a queued or running EasySourceFlow job'). It distinctively separates this tool from siblings like easysourceflow_retry_job or easysourceflow_get_job.

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?

While the description implies usage when cancellation is needed, it provides no explicit guidance on when not to use or how it compares to alternatives such as easysourceflow_retry_job. Usage is implied but not directly addressed.

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