SassyMCP

Official

Overview Schema Source Related Servers Discussions Admin

sassy_hooks_deactivate

Idempotent

Deactivate a specific active hook or clear all active hooks for this session. Use when a playbook no longer applies or before activating a different set of hooks.

Instructions

Mutating: removes hooks from the in-memory active list for this session. hook_name is optional; pass a specific active hook name to deactivate just it, or pass nothing to clear all active hooks at once. Returns {"deactivated": name} on success or {"status": "all hooks deactivated"} when clearing; attempting to deactivate a hook that is not active returns an error. Use it when a playbook no longer applies to the task or you want a clean slate before activating a different one; use sassy_hooks_list to see which hooks are currently active.

Input Schema

TableJSON Schema

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

First observedv0.1.0Jul 31, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=false and idempotentHint=true, and the description aligns with that. It adds valuable context beyond annotations: the session-scoped nature, the optional behavior (specific hook vs. clearing all), and the error case for non-active hooks. It does not over-explain but covers the key behavioral nuances.

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 compact and front-loaded with the core purpose ('removes hooks'). Every sentence adds value: behavior, return formats, error case, and usage context. No fluff or redundancy.

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 simple tool with one optional parameter, the description covers all necessary context: what the tool does, when to use it, how to use it, expected returns, and error behavior. The presence of an output schema is not needed because return shapes are described explicitly.

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 schema has one optional parameter with no description (coverage 0%), but the description fully compensates. It explains that hook_name is optional, that passing a name deactivates that specific hook, and that omitting it clears all hooks. This is complete parameter documentation.

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 clearly states the action (removing hooks from the in-memory active list) and the resource (hooks). It distinguishes this tool from siblings like sassy_hooks_activate and sassy_hooks_list by naming the specific scope (session) and the contrast with listing active hooks.

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 gives explicit when-to-use guidance: when a playbook no longer applies or you want a clean slate before activating a different hook. It also names the alternative sassy_hooks_list for inspecting active hooks, providing a clear decision path for the agent.

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

Deploy Server