Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Save Database

save_database

Save the current or specified IDA Pro database to disk as an .i64 file, with optional instance selection when multiple databases are open.

Instructions

Save the current (or specified) IDA database to disk (.i64).

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

Input Schema

NameRequiredDescriptionDefault
timeoutNoTimeout in seconds
instance_idNoREQUIRED whenever more than one database is open (from open_database's result or list_databases()); optional only while exactly one instance is live.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • changedInput schema / properties / instance_id / description
      Previous value: -"Instance id; defaults to the current target"New value: +"REQUIRED whenever more than one database is open (from open_database's result or list_databases()); optional only while exactly one instance is live."
  2. First observedv0.9.7

TDQS

B3.1/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 behavioral burden. It states that the tool writes to disk, but does not explain overwrite behavior, permissions, failure modes, whether it blocks, or what is returned. For a mutation/persistence operation with no annotation coverage, this is a meaningful gap.

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 a single front-loaded sentence with no wasted words. It is compact and immediately states the action and target format.

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?

Given a simple two-parameter save operation with full schema coverage and no output schema, the description is minimally adequate. However, the lack of annotations and the unresolved overlap with save_idb leave an agent without enough context to choose confidently between the two or anticipate save-specific behavior.

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 both parameters are already documented clearly. The description's phrase 'current (or specified)' adds a small amount of context about instance selection, but the schema does the substantive work, including the multi-instance requirement for instance_id.

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?

The description states a clear verb and resource: saving an IDA database to disk in .i64 format. It is easy to understand, but it does not distinguish this tool from the sibling save_idb, which appears to serve a closely related or identical purpose.

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?

The description gives no guidance on when to use save_database instead of save_idb, nor does it explain preconditions such as whether analysis must be complete. It also does not say when not to use it or what happens with multiple open databases beyond the schema's instance_id note.

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