Skip to main content
Glama

全局急停熔断开关

app_emergency_trip

Force-stops all Codex sessions and in-flight API requests in one UI-only emergency action, then downgrades global Turbo passthrough to shadow isolation without resending.

Instructions

UI 专用:一次性强杀所有会话运行中的 Codex 进程树与在途 API 请求(绝不重发),并将在途全局 Turbo 直通安全降级回影子隔离。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "app_emergency_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the blast radius (all sessions, process trees, in-flight requests), that nothing is retried, and that global Turbo passthrough is destructively downgraded to shadow isolation. It omits whether the tripped state persists, how to recover, and what 'UI-only' means for non-UI callers.

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 dense sentence that front-loads the caller restriction and the destructive action before the side effect. No filler, no restatement of the title.

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 highly destructive, annotation-less, no-output-schema tool it covers what gets killed, that it is one-shot, and the global state downgrade — the essentials. It still leaves the 'reason' parameter and post-trip recovery/persistence state unexplained, which matters given the irreversibility of the action.

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 the single 'reason' parameter, and the description never mentions it at all — no format, length, or whether it is recorded in logs/audit. For a destructive global action, the audit-trail semantics of 'reason' would be the most valuable thing to explain.

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?

States a specific verb and full scope: force-kill all sessions' running Codex process trees and in-flight API requests, plus a secondary effect (safe downgrade of global Turbo passthrough to shadow isolation). The 'all sessions' scope plus 'one-shot' distinguishes it from the per-job siblings like app_abort_job and sidedesk_abort_job without needing to name them.

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' qualifier and 'one-shot / never retry' framing imply this is the emergency global stop rather than the per-job abort, but no alternative is named and no explicit when-to-use/when-not condition is given. An agent must infer the routing from scope alone.

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