SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_setup_tools

Destructive

Check, install, or add external tools (Tesseract, ADB, scrcpy, Nmap, Plink, Cloudflared) to PATH. Use check for a read-only report, install to add missing required tools.

Instructions

Mutating installer for external tool dependencies; use action=check for the read-only report. The action parameter (default "check") accepts check, install, install_required, add_to_path. The tool_name parameter is required only for action=install and must be one of tesseract, adb, scrcpy, nmap, plink, cloudflared. action=check reports each tool as found with its path and required flag; only tesseract is required (OCR/vision need it unconditionally), while adb/scrcpy serve Android tools and plink serves SSH/Linux tools. action=install_required installs every missing required tool; action=install installs the named tool, both via the host package manager (winget, brew, or sudo apt-get) with a 180 second per-package timeout, so installs take minutes. Run action=add_to_path (or restart) afterward. For a read-only scan also covering Chrome and Python packages, use sassy_setup_check_tools.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	No		check
`tool_name`	No

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_setup_toolsOutput"New value: +"sassy_setup_toolsDictOutput"

First observedv0.1.0Jul 31, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already mark the tool as destructive and non-read-only; the description adds substantial behavioral context: package-manager use (winget, brew, sudo apt-get), a 180-second per-package timeout, minute-scale installs, required-tool semantics, and the post-install add_to_path step. There is no contradiction with the 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 every sentence earns its place: mutating identity, action enum, tool_name constraints, required-tool mapping, install mechanics and timeout, follow-up step, and sibling differentiation. It front-loads the critical mutating/read-only distinction.

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 multi-action installer with destructive side effects and external package-manager behavior, this description covers supported actions, target tools, platform-specific package managers, timeout expectations, and the required follow-up step. Since an output schema exists to document return shape, nothing essential is missing.

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

Parameters5/5

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

The input schema has bare unconstrained strings with 0% description coverage and no enums. The description fully compensates by enumerating the legal action values and default, defining exactly when tool_name is required, and listing its allowed values: tesseract, adb, scrcpy, nmap, plink, cloudflared.

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 opens with 'Mutating installer for external tool dependencies,' a specific verb/resource pairing, then enumerates four actions with distinct outcomes. It explicitly distinguishes itself from sibling sassy_setup_check_tools for read-only scans, so an agent can tell them apart without opening the schema.

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?

It says explicitly to use action=check for the read-only report and routes deeper read-only scanning to sassy_setup_check_tools. It also specifies when tool_name is required, which actions perform installs, and that add_to_path should be run afterward. This gives clear when/when-not guidance.

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

Deploy Server