Skip to main content
Glama
Sign In
Ghidra MCP Server

Ghidra MCP Server

by bethington
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

load_tool_group

Load all tools in a specified category, or pass "all" to enable every available tool. Use it to activate the Ghidra capabilities needed for a task.

Instructions

Load all tools in a category. Accepts a category name or "all" to load everything.

Use list_tool_groups() to see available categories.

Args: group: Category name (e.g. "function", "datatype") or "all"

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

Input Schema

NameRequiredDescriptionDefault
groupYesCategory name (e.g. "function", "datatype") or "all"

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent knows this mutates state without being destructive. The description implies loading makes tools available but never explains whether it accumulates or replaces already-loaded groups, or whether it affects the session's tool set beyond this call.

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?

Two short sentences followed by a minimal Args block; the core action and the 'all' option are front-loaded. The Args section is redundant with the schema but not harmful.

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

Completeness3/5

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

With one fully documented parameter and no output schema, most requirements are met. However, for a state-changing tool the description omits what happens to the current tool set after loading, which an agent needs before invoking it.

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?

Schema description coverage is 100% and already documents 'group' with the same examples and the 'all' sentinel. The Args block in the description merely restates the schema, adding no new semantics such as case sensitivity or invalid-name behavior.

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?

States a specific verb and resource ('Load all tools in a category') and the scope switch ('all'). It does not explicitly contrast with unload_tool_group, but the load/unload pairing makes the distinction fairly apparent.

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?

Directs the agent to call list_tool_groups() first to discover valid categories, which is a concrete prerequisite. It stops short of stating when not to use it or naming alternatives such as search_tools.

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