Skip to main content
Glama

中止运行中的副席任务

sidedesk_abort_job

Stops a running job by terminating its Codex process tree or OpenAI API stream, then marks the task aborted without auto-retry.

Instructions

立即中止运行中的 Codex 进程树或 OpenAI API 流式请求,并将任务标记为 aborted(绝不自动重发)。

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": {
      "jobId": "<jobId>"
    },
    "name": "sidedesk_abort_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes要中止的 jobId
reasonNo可选:中止原因

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?

With no annotations supplied, the description carries the behavioral burden and does meaningful work: it discloses that the action is immediate and destructive (kills a process tree / cancels a streaming request) and that the job is marked aborted with no automatic resend. It stops short of stating permissions, side effects on partial output, or what the caller receives.

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?

A single sentence, front-loaded with 立即中止 and the targets, followed by the outcome and a short parenthetical guarantee. Nothing is wasted.

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 simple two-parameter action with full schema coverage and no output schema, the description covers what is killed and what state results. The only real gap is disambiguation from app_abort_job, which an agent needs in order to pick the correct 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 coverage is 100% — both jobId and the optional reason already have descriptions in the schema. The prose adds no meaning beyond that (e.g., no guidance on where jobId comes from or how reason is surfaced).

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?

The description gives a specific verb (中止/abort) and concrete resources (Codex 进程树、OpenAI API 流式请求), plus the resulting state (标记为 aborted). It does not, however, distinguish this tool from the similarly named sibling app_abort_job, so an agent cannot tell which abort variant applies to a given 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?

Usage is only implied by the qualifier 运行中 — call it on a job that is currently running. There is no explicit when-not guidance, no mention of what to do if the job already finished, and no pointer to app_abort_job as the alternative.

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