Skip to main content
Glama

UI 中止任务

app_abort_job

Terminate a running Codex process tree or interrupt an active streaming API request by job ID to stop stalled or unwanted work.

Instructions

UI 专用:强杀运行中的 Codex 进程树或中断 API 流式请求。

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": "app_abort_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key trait: this is a destructive force-kill of a process tree or an abort of a streaming request. It omits the aftermath — whether partial output is lost, what state the job is left in, whether it is reversible, and what the call returns.

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?

A single compact sentence with the scope qualifier front-loaded and zero filler. It is efficient, though its brevity leaves several gaps that a slightly longer definition would have closed.

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?

For a destructive two-parameter tool with no annotations, no output schema, and no parameter docs, the definition does not fully cover what an agent needs to call it safely — notably the job-state aftermath and how jobId is sourced. It is adequate only because the core destructive action is stated plainly.

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 0%, so the description must compensate, and it does not: neither jobId (required) nor reason is mentioned. jobId is self-evident from its name and a job-abort context, but reason and how to obtain a jobId remain undocumented in both places.

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 target: force-kill the running Codex process tree or interrupt an API streaming request. The "UI 专用" prefix scopes it to UI-driven aborts, which partly distinguishes it from the sibling sidedesk_abort_job, though it never names that alternative or explains the difference.

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 UI-only framing implies the usage context (aborting a job from the UI), but there is no explicit when-to-use vs. when-not, and no guidance on choosing between this and sidedesk_abort_job. An agent must infer the selection rule.

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