Skip to main content
Glama
sassyconsultingllc

SassyMCP

Official
by sassyconsultingllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sassy_tool_group_toggle

Idempotent

Enable or disable a tool group to trim context usage or activate dormant capabilities, with automatic refresh notification for compatible clients.

Instructions

Mutating: flips a tool group's always_load flag in the running server process, enabling (enable=true, default) or disabling (enable=false) its modules, and attempts a tools/list_changed notification so capable clients (Claude Code, Cursor) refresh automatically. Clients that do not handle it (Claude Desktop today) need a manual server restart. group must be an exact group name (core, infrastructure, android, system, forensics, linux, github_quick, github_full, persona, utility, setup, memory, updater, combos, prompts); an unknown name returns an error listing the valid groups. Returns status, the group's modules, and whether the notification was sent. Use it to trim context by disabling heavy unused groups like github_full, or to load dormant capability on demand; check sassy_tool_groups first for current load status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupYes
enableNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.15.1
    • 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_tool_group_toggleOutput"New value: +"sassy_tool_group_toggleDictOutput"
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

The description goes well beyond annotations by detailing the live-server mutation, the attempted tools/list_changed notification, client-specific behavior requiring restart, unknown-group error behavior, and return contents. This gives the agent a complete behavioral picture with no contradictions.

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 information-dense and well-structured, opening with the mutating nature and action before covering notification, acceptable values, return values, and use cases. The long list of group names is justified because the schema lacks enums or descriptions.

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 mutating toggle with two parameters Games, the description covers inputs, valid values, side effects, client behavior, return summary Games, and usage rationale. The output schema covers the return structure, while the description fills all other contextual gaps.

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 'enable=true, default' and 'enable=false', requires an exact group name, lists all valid group names, and explains the error for unknown names. This adds meaning far beyond the bare schema properties.

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 verb and resource: 'flips a tool group's always_load flag' and explains enabling/disabling modules. This clearly distinguishes it from sibling tools like sassy_tool_groups by focusing on mutation rather than inspection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit use cases: 'trim context by disabling heavy unused groups like github_full' or 'load dormant capability on demand.' It also directs the agent to check sassy_tool_groups first for current load status, providing clear context, though it does not explicitly list when-not-to-use cases.

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

Deploy Server

Other Tools