SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_hooks_list

Read-onlyIdempotent

List all registered operational hooks with metadata: names, owning modules, descriptions, trigger phrases, count, and active hooks. Use to discover available playbooks before activating one.

Instructions

Read-only. Lists every registered operational hook with metadata only (no full instructions): name, owning module, one-line description, and trigger phrases, plus a count and the names of currently active hooks. Takes no parameters. Use this to discover which playbooks exist before calling sassy_hooks_activate; if you know the user's request but not the right hook, use sassy_hooks_suggest to rank matches against the request text first.

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_hooks_listOutput"New value: +"sassy_hooks_listDictOutput"

First observedv0.1.0Jul 31, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive safety, so the bar is lower. The description adds valuable behavioral context beyond annotations by stating it returns 'metadata only (no full instructions)' and includes a count plus names of currently active hooks. This clarifies a significant limitation an agent would otherwise discover only after calling the tool.

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?

Three tightly-written sentences front-load the essential listing behavior, then state the lack of parameters, then give usage routing. Every sentence earns its place, with no filler or repeated annotation details beyond a single-word 'Read-only.'

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 listing tool with rich annotations and an output schema, the description is complete: it states scope, output composition, what is excluded, and how to route to alternatives. Nothing needed for correct invocation 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, for which the baseline is 4. The description redundantly states 'Takes no parameters,' which is already obvious from the empty schema but removes any ambiguity. No additional parameter semantics are needed.

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 uses a specific verb 'Lists' with a precise resource ('every registered operational hook') and clearly defines the scope and output ('metadata only: name, owning module, one-line description, trigger phrases, count, active hooks'). This makes it immediately distinguishable from sibling tools like sassy_hooks_activate, sassy_hooks_suggest, and sassy_hooks_deactivate.

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?

Explicit usage guidance is provided: use this tool to discover playbooks before calling sassy_hooks_activate, and use sassy_hooks_suggest instead when the request is known but the right hook is not. This names both when and when-not to use the tool, fully meeting the criterion.

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

Deploy Server