SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_hooks_activate

Idempotent

Activate a named hook to receive structured expert guidance for a matching task domain. Returns a step-by-step playbook with tool usage and precautions.

Instructions

Mutating session state: appends the named hook to the in-memory active hook list (hooks can be stacked). Read the playbook carefully afterward. hook_name is the exact hook ID; if not found, the tool returns an error plus the available hook names and substring-based suggestions. On success it returns the full expert playbook: name, owning module, description, and step-by-step instructions covering which tools to use, in what order, what to look for, and what not to do. Use sassy_hooks_list first to discover valid hook names. Activate a hook when a task matches a known domain and you want structured expert guidance; use sassy_hooks_deactivate to unload it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`hook_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_hooks_activateOutput"New value: +"sassy_hooks_activateDictOutput"

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?

The description goes well beyond the annotations by explaining that hooks can be stacked, that the hook list is in-memory, and what happens on both success and failure. It also tells the agent to read the returned playbook carefully. The only slight tension is 'appends' vs the idempotentHint, but stacking is described as possible rather than guaranteed, so no contradiction is evident.

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 adds value: the mutating effect is front-loaded, followed by the prerequisite, error behavior, success return, and when to use alternatives. It is detailed but not bloated, and no sentence is redundant with the schema or annotations.

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 one-parameter tool with an output schema, the description covers the essential context: what the hook is, how to find it, what to expect on failure, what is returned on success, and how to undo the action. 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.

Parameters5/5

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

Schema coverage is 0%, but the description fully compensates: it defines hook_name as 'the exact hook ID,' describes lookup-failure behavior, and points to sassy_hooks_list for discovering valid names. This adds meaning well beyond the bare property name in the schema.

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 action and resource: it 'appends the named hook to the in-memory active hook list.' It also clarifies the mutating nature and distinguishes itself from related hook tools like sassy_hooks_list and sassy_hooks_deactivate, so an agent can tell it apart at a glance.

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?

Usage is explicitly conditioned: 'Activate a hook when a task matches a known domain and you want structured expert guidance.' It also tells the agent to use sassy_hooks_list first and sassy_hooks_deactivate to unload, providing clear when-to-use and when-not-to-use guidance.

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

Deploy Server