SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_session_stop

DestructiveIdempotent

Terminate a named persistent session, force-kill after 5s if needed, remove it, and return exit code and last 3000 characters of unread output.

Instructions

Mutating: terminates a named persistent session's process (graceful terminate, force kill after 5s), removes the session, and returns the name, exit code, and the last 3000 characters of unread output. Fails if the session does not exist. Use it to clean up a session you started; use sassy_session_stop_all to kill everything at once.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.15.1Sep 18, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "title": "Result",
-    "type": "string"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

changedOutput schema / title

Previous value: -"sassy_session_stopOutput"New value: +"sassy_session_stopDictOutput"

First observedv0.1.0Jul 31, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, but the description adds valuable behavioral details: the graceful terminate/force kill after 5s, removal of the session, return values, and failure condition. It also notes it's mutating, which aligns with annotations. No contradiction.

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 paragraph front-loads the most critical information (mutating, termination behavior, removal, return values) before the usage guidance. Every sentence adds value with no redundancy.

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

Completeness5/5

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

Given the tool's moderate complexity (single parameter, no nested objects, no enums) and the presence of an output schema (which likely details return values), the description covers all necessary aspects: behavior, failure mode, and usage. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain the 'name' parameter. It does by referring to 'named persistent session', implying the name identifies which session to stop. This is adequate given only one parameter and no enum.

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?

The description clearly states the action ('terminates... removes... returns'), the specific resource ('named persistent session'), and its behavior (graceful terminate, force kill after 5s). It is easily distinguished from siblings like sassy_session_stop_all and other session tools.

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

Usage Guidelines5/5

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

Explicitly says 'Use it to clean up a session you started' and contrasts with sassy_session_stop_all for killing everything at once. This provides clear when-to-use guidance and distinguishes from the sibling.

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

Deploy Server