stop_sessionStop an active session by id to halt traffic capture and trigger an automatic rescan of captured entries for findings.
Stop an active session. After stopping, the engine automatically rescans the captured entries for findings.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Session id from start_session. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly=false, idempotent=true, and destructive=false, so the safety profile is known. The description adds genuinely new behavioral context beyond the annotations: stopping triggers an automatic rescan of captured entries for findings, which an agent should anticipate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, action first, side effect second. Nothing is wasted and the most important information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description does the remaining work: it discloses the consequential post-stop rescan and the tool is simple (one required param, full schema coverage, annotations present). Only the resulting session state (e.g., whether it can be resumed or must be restarted) is left unstated.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%; the single parameter 'id' is documented as 'Session id from start_session.' The description adds no additional parameter meaning, so the schema carries the load and baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Stop') and resource ('active session'), and the 'active' qualifier scopes it away from list_sessions/get_session. However, it never distinguishes itself from the closely related delete_session sibling, leaving the agent to infer the difference.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit when-to-use guidance, no prerequisites, and no naming of alternatives such as delete_session (removal) or rescan_findings (which overlaps with the auto-rescan behavior described). The 'active session' phrasing implies a precondition but does not state it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.