Skip to main content
Glama
Sign In
Kanysh Basic

Kanysh Basic

by almukhanomr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

job_cancel

Cancel a queued or running job by job_id, stopping the worker and any child simulator while keeping already published artifacts; check job status afterward.

Instructions

Request cancellation of a queued or running job (job_id). Stops the worker and any child simulator; already published artifacts are kept. Check job_status afterwards.

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": {
      "request": "<request>"
    },
    "name": "job_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesTool arguments object (all fields documented; Z is positive upward).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations say non-read-only, non-destructive, non-idempotent; the description adds real value beyond them by disclosing cascading effects ('stops the worker and any child simulator') and data preservation ('already published artifacts are kept'). It stops short of stating what happens on a second cancel (relevant given idempotentHint=false) or whether cancellation is guaranteed to succeed.

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 sentences, front-loaded with the verb and target, followed by consequences and the recommended follow-up. No filler and no repetition of schema fields.

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?

With no output schema, the description correctly supplies the effect description, the artifact-retention rule, and the next step (job_status). Only gap is the absence of any note on failure modes or partial cancellation, which matters for a single-parameter mutation tool.

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%, including a documented job_id with format example 'job-…', so the schema carries the semantics. The description only restates the parameter name in parentheses and adds no format or sourcing detail beyond it, making 3 the correct baseline.

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?

States a specific verb and resource with scope: 'Request cancellation of a queued or running job,' narrowing to job-job state rather than any workflow. It does not explicitly contrast with the similarly-purposed sibling workflow_cancel, so differentiation is left to the agent's inference from the resource noun.

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?

Implied usage by naming job states ('queued or running') and a follow-up action ('Check job_status afterwards'), which tells the agent the intended lifecycle. However, no explicit when-not condition and no reference to workflow_cancel as the alternative for workflow jobs.

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