Skip to main content
Glama
Sign In
Ghidra MCP Server

Ghidra MCP Server

by bethington
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

unload_tool_group

Unloads all tools in a specified category to reduce active tool groups; default protected groups are excluded.

Instructions

Unload all tools in a category. Default groups are protected from unloading.

Args: group: Category name to unload

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": "unload_tool_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesCategory name to unload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv7.0.0
    • addedInput schema / properties / group / description
      Added value: +"Category name to unload"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "unload_tool_groupOutput",
-  "type": "object"
-}New value: +null
  2. First observedv5.15.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds a useful behavioral constraint: default groups cannot be unloaded. It still does not explain whether unloading is reversible or what happens to currently active tools.

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?

The description is short and front-loaded with the main action and protection rule. The Args section repeats schema information, which is mildly redundant but not harmful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with annotations covering its safety profile and no output schema, the description is mostly complete. It could mention the inverse load_tool_group operation or reversibility, but no critical information is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

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

There is one parameter and schema description coverage is 100%, so the schema already documents the group argument. The description repeats the schema text but adds no further syntax or selection guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: unload all tools in a category. It distinguishes unloading from loading via the sibling load_tool_group, though it does not explicitly name that sibling.

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

Usage Guidelines3/5

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

It gives one constraint — default groups are protected from unloading — but does not explain when to use this versus load_tool_group or list_tool_groups. The usage context is implied rather than explicit.

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