SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_setup_status

Read-onlyIdempotent

Check the setup state of an unknown machine with this read-only report. It shows completed setup, auth and integration status, config paths, and required next steps if incomplete.

Instructions

Read-only aggregated setup report with no parameters. Reports setup_complete, persona file existence/size/path, auth state (whether SASSYMCP_AUTH_TOKEN is set in the environment, whether ~/.sassymcp/tokens.json exists, and overall auth_active), integrations (GitHub token configured plus the saved GitHub username, SSH configured plus the saved SSH host), the config file path with its key names, the SassyMCP data directory, and the files currently in it. If setup is not complete it includes an action_required field pointing at the next steps. This is the best first call when diagnosing an unknown machine or confirming what first-run steps remain. It never modifies anything. To fix what it reports as missing, call sassy_setup_wizard for the persona, sassy_setup_github or sassy_setup_ssh for integrations, or sassy_setup_tools for dependencies.

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_setup_statusOutput"New value: +"sassy_setup_statusDictOutput"

First observedv0.1.0Jul 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=fals. The description adds meaningful behavioral context: 'It never modifies anything,' the conditional presence of action_required, and the details of what is reported (e.g., 'whether SASSYMCP_AUTH_TOKEN is set' rather than its value). It fully discloses the tool's reporting scope and non-mutating nature beyond the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but front-loaded with the core purpose, and every sentence contributes either report contents, usage guidance, or sibling routing. The 'never modifies anything' sentence is redundant with annotations, and the field list is dense, but the structure is clear and each section earns its place.

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 has no parameters, an output schema, and strong annotations, the description covers all the agent needs: what the report contains, the conditional action_required field, when to call it, and which sibling tools to use next to remediate issues. Nothing essential 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 and the schema coverage is 100% (empty properties object), so the baseline is 4. The description correctly states 'with no parameters,' and since there are no parameters to document, it cannot add more meaning. No gaps exist.

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 'Read-only aggregated setup report,' a specific verb and resource, and enumerates the exact fields reported (setup_complete, persona file, auth state, integrations, config path, data directory). It distinguishes itself from sibling setup tools by declaring it 'the best first call' for diagnosing an unknown machine, making its role unambiguous.

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 explicitly states when to use the tool: 'best first call when diagnosing an unknown machine or confirming what first-run steps remain.' It also names the precise alternatives for fixing issues: 'call sassy_setup_wizard for the persona, sassy_setup_github or sassy_setup_ssh for integrations, or sassy_setup_tools for dependencies.' This is explicit routing with no inference needed.

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

Deploy Server