Skip to main content
Glama
Ghidra MCP Server

Ghidra MCP Server

by bethington

list_tool_groups

Read-only

Lists all available tool groups with tool counts, loaded status, and tool names so you can identify and load the group needed for Ghidra analysis.

Instructions

List all available tool groups with their tool counts and loaded status.

Returns each category with: tool count, loaded status, and tool names. Use load_tool_group(group) to load a group's tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tool_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv7.0.0
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "list_tool_groupsOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv5.15.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real value by disclosing the return payload (tool count, loaded status, tool names), which is the "

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?

Three short, front-loaded sentences with no filler. The second sentence partially restates the first (tool count / loaded status appear twice), which is the only minor waste.

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 zero-parameter discovery tool with no output schema, the description covers purpose, the shape of the returned data, and the natural next action. Nothing an agent needs in order to call it or use the result is missing.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The mention of a "group" argument for load_tool_group correctly points at the sibling's parameter rather than implying one here.

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 ("List all available tool groups") plus scope detail (tool counts and loaded status). It implicitly separates itself from load_tool_group and search_tools/check_tools, but never explicitly contrasts with those siblings.

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?

"Use load_tool_group(group) to load a group's tools" gives clear follow-on context, framing this as the discovery step before loading. It lacks any explicit when-not or comparison to check_tools/search_tools, so it stops short of a 5.

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