Skip to main content
Glama

sassy_tool_group_toggle

Idempotent

Enable or disable a tool group so it loads or stays unloaded on the next server restart, trimming context by excluding heavy unused groups or adding dormant capability on demand.

Instructions

Mutating: sets a tool group's always_load flag so the group loads (enable=true, default) or stays unloaded (enable=false) on the NEXT server start. Module loading is resolved once at startup, so this cannot add or remove tools from a running session — restart the server process for the change to take effect. 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 takes_effect (next server restart). 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "group": "<group>"
    },
    "name": "sassy_tool_group_toggle"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYes
enableNo

Output 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.9/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), it discloses the deferred-effect model — the flag only applies on the NEXT server start and requires a process restart — plus the error behavior for unknown group names and the shape of the response. This is exactly the kind of context annotations cannot express.

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?

It is front-loaded with the mutating nature and the restart caveat, and every sentence carries information. The restart timing is stated twice (once as a warning about running sessions, once in the takes_effect return note), which is a minor redundancy in an otherwise dense, well-ordered paragraph.

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 two-parameter mutation tool with an output schema, the description covers the mutation's timing, its valid inputs, its failure mode, and its sibling relationship. An agent has everything needed to call it correctly and to set user expectations about when the change lands.

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% and neither parameter has an enum or description, so the description does all the work: it enumerates the complete valid group set, states that names must match exactly, defines enable=true/false semantics, and notes enable=true is the default. Both parameters are fully interpretable from the description alone.

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 a specific verb+resource+mechanism: it sets a tool group's always_load flag. It also distinguishes itself from the sibling sassy_tool_groups, which it explicitly redirects to for reading current load status, so an agent can tell read from write without opening either schema.

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 states concrete when-to-use cases (trim context by disabling heavy unused groups like github_full; load dormant capability on demand) and names the prerequisite alternative (check sassy_tool_groups first for current status). It also gives an explicit when-not-to-expect-effect: nothing changes in a running session.

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