SassyMCP

Official

by sassyconsultingllc

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

sassy_session_list

Read-onlyIdempotent

Retrieve all persistent terminal sessions as JSON to identify active and dead processes before managing them.

Instructions

Read-only. Lists all persistent terminal sessions as JSON: name, shell, pid, alive flag, uptime in seconds, output buffer size, exit code, plus a total count. Dead sessions remain listed until stopped. Use it to see what is running before sassy_session_read, sassy_session_send, or sassy_session_stop; auto-detached sassy_shell calls also appear here.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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_listOutput"New value: +"sassy_session_listDictOutput"

First observedv0.1.0Jul 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds materially useful behavioral context beyond annotations: dead sessions remain listed until stopped, and auto-detached sassy_shell calls appear in this list. These are behavioral traits an agent needs to interpret the list correctly.

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?

The description is compact and efficiently front-loaded: 'Read-only. Lists all persistent terminal sessions as JSON' immediately conveys scope and format. The remaining sentences add field detail, dead-session behavior, and usage guidance without a single wasted clause.

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?

For a zero-parameter, read-only list tool with an output schema and rich annotations, the description covers everything needed to call it correctly: what it lists, the exact fields returned, when to use it, and the edge case of auto-detached sassy_shell calls. Nothing relevant 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?

The tool has zero parameters, so the schema covers all inputs trivially. Baseline for zero-parameter tools is 4, and the description appropriately focuses on output and behavior rather than input semantics, since there are no parameters 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?

The description states a specific verb ('Lists'), a clear resource ('all persistent terminal sessions'), and the output format ('as JSON'), then enumerates the returned fields. It further distinguishes itself from sibling session operations by noting auto-detached sassy_shell calls also appear here, so an agent can tell it apart without ambiguity.

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?

The description explicitly states when to use it: 'Use it to see what is running before sassy_session_read, sassy_session_send, or sassy_session_stop.' It also clarifies the scope edge case of auto-detached sassy_shell calls, giving the agent clear context for when this listing tool is relevant versus alternatives.

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

Deploy Server