Skip to main content
Glama
Sign In
Ghidra MCP Server

Ghidra MCP Server

by bethington
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

check_tools

Read-only

Verify whether specified Ghidra MCP tools are callable now and return each status—callable, not_loaded, or not_found—so you can diagnose missing or unloaded capabilities before calling them.

Instructions

Check if specific tools are callable right now. Returns status for each tool: "callable", "not_loaded" (exists but group not loaded), or "not_found" (doesn't exist).

Args: tools: Comma-separated tool names, e.g. "rename_symbol,batch_set_comments,analyze_function_completeness"

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": {
      "tools": "<tools>"
    },
    "name": "check_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolsYesComma-separated tool names, e.g. "rename_symbol,batch_set_comments,analyze_function_completeness"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv7.0.0
    • addedInput schema / properties / tools / description
      Added value: +"Comma-separated tool names, e.g. \"rename_symbol,batch_set_comments,analyze_function_completeness\""
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "check_toolsOutput",
-  "type": "object"
-}New value: +null
  2. First observedv5.15.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, and there is no output schema, so the description's enumeration of the three return statuses carries real weight — it tells the agent how to interpret results. It stops short of noting batch limits or ordering guarantees, keeping it from a 5.

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?

Front-loaded with the purpose and return semantics, and short overall. The Args block is a near-exact duplicate of the schema description, which is mildly wasteful but not harmful.

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?

With no output schema, the description must explain return values — and it does so precisely with all three statuses defined. A single required parameter is fully documented, so an agent has everything needed to call it and interpret the result.

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 coverage is 100% and the description's Args section simply repeats the schema's parameter text verbatim, including the same example. No additional formatting or edge-case guidance is added, so the baseline 3 applies.

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 and resource ('Check if specific tools are callable right now') and enumerates the three possible statuses, so an agent knows exactly what question this tool answers. It is clearly distinguishable from siblings like search_tools or load_tool_group.

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?

Usage is implied rather than stated: the 'not_loaded' vs 'not_found' distinction hints that you'd follow up with load_tool_group or abandon the call, but no alternative is named and no explicit when-to-use condition is given. An agent can infer the workflow but must do the routing itself.

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