Systems Manager

Stop System Trace

stop_system_trace

DestructiveIdempotent

Stop a kernel-level event trace session by name to end event collection and release associated tracing resources.

Instructions

Stop a kernel-level event trace.

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": {
      "session_name": "<session_name>"
    },
    "name": "stop_system_trace"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Explicit confirmation. Pass true when the client cannot answer an approval prompt.
`session_name`	Yes	Name of the trace session

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.9Nov 3, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "Explicit confirmation. Pass true when the client cannot answer an approval prompt.",
+  "type": "boolean"
+}

First observedv2.2.5Oct 24, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is carried by structured data. The description adds only the "kernel-level" qualifier and says nothing about what happens to buffered trace data, whether the session definition persists, or how an unknown session_name is handled.

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 front-loaded sentence with zero filler; nothing needs trimming. Brevity here edges toward under-specification rather than verbosity, which is penalized in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, session-scoped operation this is too thin: it never warns that an in-progress capture ends, never indicates the required state, and never hints at what the (existing) output schema returns. Output schema and annotations reduce the burden, but the gap is still notable.

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% and both parameters (session_name, confirm) carry their own descriptions, so the schema does the documentation work. The description adds no extra meaning such as session-name format, case sensitivity, or the semantics of stopping an already-stopped session.

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 ("Stop") and resource ("kernel-level event trace"), so an agent knows exactly what is being terminated. It does not explicitly name its counterpart sibling start_system_trace, but the opposite direction is obvious enough from the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites (does the session have to be running?), and no word about the confirm parameter or what to do when a prompt is unavailable. The only routing signal available is the sibling name start_system_trace, which the description never references.

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