SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_session_send

Destructive

Send text to a persistent session, appending a newline automatically, and receive the new output. Use it to interact with REPLs, prompts, or dev servers that need ongoing input.

Instructions

Mutating: types into a live persistent session like a terminal, with a newline appended automatically, and returns the last 5000 characters of new output after a brief pause. The input is scanned by the same gates as sassy_shell: blocklist matches and delete keywords (rm, del, Remove-Item) are refused here, because session input cannot be safely staged — use sassy_safe_delete for removals instead. Fails if the session does not exist or has exited. Use it to interact with REPLs, prompts, and dev servers running in a session; use sassy_shell for one-shot commands.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`input_text`	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_sendOutput"New value: +"sassy_session_sendDictOutput"

First observedv0.1.0Jul 31, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description discloses mutation, the newline append, the 5000-character return limit, the pause, the blocklist/delete-keyword refusal, and the failure condition (session does not exist or exited). This goes well beyond the annotations, which only say destructiveHint=true. No contradiction with 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?

The description is dense but well-organized: behavior first, then safety constraints, then usage guidance. Every sentence adds value, and it's not bloated.

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 mutating session tool with an output schema, the description covers behavior, failure modes, safety gates, and alternatives. Nothing critical is missing for an agent to invoke it correctly.

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 description coverage is 0%, so the description must compensate. It explains what input_text does (typed into session) and what name refers to (the session), but doesn't add format details like whether name is a session ID or label. Still, the description gives enough context for the two obvious parameters.

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 ('types into a live persistent session like a terminal'), the resource (a session), and the key behavior (appends newline, returns last 5000 chars after a pause). It also distinguishes itself from sassy_shell and sassy_safe_delete, making it clear what this tool is for.

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 when to use it ('interact with REPLs, prompts, and dev servers running in a session') and when not to ('use sassy_shell for one-shot commands', 'use sassy_safe_delete for removals'). This is strong routing guidance.

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

Deploy Server