Skip to main content
Glama
Sign In
ih8sn1ff

ih8sn1ff

by ih8w1nd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ghidra_import

Import binaries into a Ghidra project headlessly, with optional full analysis or none, to prepare them for reverse engineering.

Instructions

Headless Ghidra import into a project (analysis: full or none).

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": {
      "binary": "<binary>",
      "project": "<project>"
    },
    "name": "ghidra_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
binaryYes
projectYes
analysisNofull
timeout_minNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says 'headless import' but does not disclose what happens to an existing project, whether it overwrites data, what permissions or environment are required, or what the output/return is. Only the analysis option is hinted at.

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?

Single sentence with no wasted words and the core action is front-loaded. The parenthetical is efficient, though the sentence is quite dense and could have been split to improve readability without adding much length.

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

Completeness2/5

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

Given four parameters, no annotations, no output schema, and 0% schema coverage, the description is too thin. It does not cover return values, side effects, or the roles of binary, project, and timeout_min, leaving the definition incomplete for a mutation-style import operation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only mentions one of four parameters (analysis) and does so with a brief value list. It adds no meaning for binary, project, or timeout_min, leaving agents to guess their formats and constraints.

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 (import) and resource (Ghidra) plus the target (a project), and highlights the analysis mode. It distinguishes from siblings like ghidra_decompile and ghidra_funcs, which operate on an already-imported binary, though it does not explicitly name them.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives or prerequisites. It does not mention that it should be run before ghidra_decompile/ghidra_funcs, nor does it describe when to choose 'full' versus 'none' analysis beyond the option name.

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