Skip to main content
Glama
Sign In
Hex-Rays IDA MCP

Hex-Rays IDA MCP

by zy723
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Save IDA database

save_database

Save the IDA database (.i64) to disk to persist reverse engineering changes such as renames, comments, types, and patches.

Instructions

Save the IDA database (.i64) to disk so renames, comments, types and patches made during reverse engineering persist.

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
instance_idNoOptional database instance id. If omitted, save the current target.

Output Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv20261008.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does state the core mutation: writing the .i64 database to disk and persisting changes. It still omits details such as overwrite behavior, permissions, and whether saving is guaranteed to target the current file, so it is only minimally adequate.

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 well-formed sentence, front-loads the action, and gives the persistence rationale without wasted words.

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 a simple save operation with a fully documented optional parameter and an output schema, the description provides enough context to call the tool correctly. Missing sibling differentiation and some mutation edge cases keep it from being fully complete.

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?

The single optional instance_id parameter is fully documented in the schema, including the default behavior when omitted. The description adds no parameter-specific detail, which is acceptable given 100% schema coverage.

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 specific verb and resource: saving the IDA database (.i64) to disk. It also clarifies the effect—persisting renames, comments, types, and patches—but does not differentiate from the sibling idb_save, which likely overlaps.

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?

It implies the tool should be used after making reverse-engineering changes so those changes persist. However, it gives no explicit when-to-use guidance versus idb_save or close_database, and no prerequisites or exclusions.

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