Skip to main content
Glama

bx_job_cancel

Idempotent

Request cancellation of a specified job by project and job ID, preserving history and completed results; remote termination is not guaranteed.

Instructions

请求取消指定作业,保留历史,不保证远端立即终止。 / Request cancellation; retain history and completed results. Remote termination is not guaranteed.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes
project_idYes

Output Schema

NameRequiredDescriptionDefault
dataYes
kindYes
productYes
api_versionYes
business_decisionYes
execution_authorizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0-rc.9-linux.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the bar is lower. The description still adds real behavioral context beyond them: history and completed results are preserved, and remote termination is explicitly not guaranteed, which sets correct expectations for an asynchronous, best-effort cancel.

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?

Two short clauses per language, front-loaded with the action and followed by the two key caveats. The bilingual duplication adds length but no wasted sentences.

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?

An output schema exists, so return values need not be described, and the cancellation caveats cover the main behavioral risk. However, with 0% schema coverage and two required parameters, leaving both identifiers entirely unexplained is a notable gap for a job-scoped mutation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both required parameters, so the description carries the full burden of explaining them. It never mentions project_id or job_id, nor their UUID format or scoping role; only the parameter names themselves convey meaning.

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: 'Request cancellation' of a specified job. An agent can tell this is a cancel operation rather than a get or submit operation without opening the schema, though it does not name a sibling alternative to contrast with.

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?

Usage is implied by the verb 'cancel' and by 'retain history and completed results', but the description never says when to prefer cancellation over alternatives such as re-running or ignoring a job, and gives no prerequisites or exclusions.

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