SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_session_read

Read-only

Read new output from a named persistent session, advancing the read cursor for incremental polling. Returns alive status and buffer size to monitor long-running processes.

Instructions

Read-only. Returns output from a named persistent session that arrived since the last read (the cursor advances, so each call yields only new text), truncated to the last 10000 characters, plus an alive flag and the total buffer size. Fails if the session name does not exist. Use it to poll long-running sessions created by sassy_session_start or auto-detached from sassy_shell (timeout over 120s) without sending input; use sassy_session_send to interact.

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_readOutput"New value: +"sassy_session_readDictOutput"

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?

The description goes well beyond the readOnlyHint annotation by disclosing that the cursor advances on each read, output is truncated to 10000 characters, an alive flag and buffer size are returned, and the call fails for nonexistent session names. These behavioral details are not visible in the schema or annotations.

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?

Every sentence carries distinct information: the core read behavior, cursor/truncation/return details, and the usage boundary with alternatives. It is front-loaded with 'Read-only' and the main purpose, and contains no filler.

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 output schema exists and the annotations cover the read-only safety profile, the description adds the missing behavioral contract: cursor semantics, truncation, return fields, failure mode, and when to use it versus sassy_session_send. Nothing needed for correct invocation is omitted.

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?

With 0% schema description coverage, the description compensates by identifying 'name' as the persistent session name and explaining that nonexistent names cause failure. It does not specify naming rules or how to enumerate valid names, but for a single required parameter this is sufficient context.

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 ('Returns output') and resource ('named persistent session'), and immediately distinguishes itself from related session tools by noting it does not send input. It clearly conveys that this is the read/poll operation among the sassy_session_* siblings.

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 says when to use this tool: to poll long-running sessions created by sassy_session_start or auto-detached from sassy_shell. It also names the alternative, sassy_session_send, for interaction, making the selection decision unambiguous.

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

Deploy Server