Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Open Database

open_database

Opens a binary or .i64 database in a headless idalib worker, creating or analyzing it and returning an instance_id required for subsequent calls.

Instructions

Open a binary or .i64 database in a headless idalib worker (creates/analyzes the .i64). Call this first. Record the returned instance.instance_id — every subsequent tool call must carry it while multiple databases are open.

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": {
      "path": "<path>"
    },
    "name": "open_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to a local executable or .i64/.idb database. A live worker with this file is attached when present; otherwise a headless idalib worker opens/creates/analyzes it.
timeoutNoOpen/analysis wait timeout in seconds (default 300)
wait_for_analysisNoWait for IDA auto-analysis to finish (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.1
    • removedInput schema / properties / extra_args
      Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Extra IDA CLI args for GUI launches"
-}
    • removedInput schema / properties / headless
      Removed value: -{
-  "default": "auto",
-  "description": "\"auto\" (default: attach, else headless worker), \"headless\"/\"true\" (force idalib worker), \"gui\"/\"false\" (launch the IDA GUI)",
-  "type": "string"
-}
    • changedInput schema / properties / path / description
      Previous value: -"Path to a local executable or .i64/.idb database. A live instance with this file is attached when present; otherwise a headless idalib worker opens/creates/analyzes it."New value: +"Path to a local executable or .i64/.idb database. A live worker with this file is attached when present; otherwise a headless idalib worker opens/creates/analyzes it."
    • removedInput schema / properties / set_current
      Removed value: -{
-  "default": true,
-  "description": "Make this database the default target (default true)",
-  "type": "boolean"
-}
  2. First observedv0.9.7

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses useful context: a headless idalib worker is used, the .i64 is created/analyzed, and the returned instance_id is required for later calls. It still omits some side-effect details, such as overwrite behavior and what happens if analysis times out.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: the main action comes first, followed by the critical sequencing instruction and the instance_id requirement. Every sentence contributes to correct invocation.

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 an open/create-and-analyze operation with a rich input schema and no output schema, the description covers the essential workflow and the key returned value, instance.instance_id. It is slightly incomplete because it does not fully describe the return shape or all side effects, but it is sufficient for correct tool selection and use.

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%, so the schema already documents path, timeout, and wait_for_analysis in detail. The description adds no parameter-specific meaning beyond saying the path is a binary or .i64 database, so baseline 3 is appropriate.

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 states a specific verb and resource: open a binary or .i64 database in a headless idalib worker, with clarification that it creates/analyzes the .i64. The phrase 'Call this first' also situates it relative to the many sibling tools that require an already-open database.

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?

It gives clear operational guidance: call this first, and record the returned instance.instance_id because every subsequent call must carry it while multiple databases are open. It does not explicitly compare against alternatives such as check_connection or list_databases, nor does it state when not to use this tool.

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