Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Force Recompile

force_recompile

Invalidate cached Hex-Rays decompilations for specific functions or all functions so IDA regenerates fresh decompiled output.

Instructions

Invalidate cached Hex-Rays decompilations so they are regenerated.

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

Input Schema

NameRequiredDescriptionDefault
timeoutNoTimeout in seconds
addressesNoFunction name(s)/address(es) to invalidate (comma-separated ok); omit to clear all cached decompilations
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 override"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

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It correctly implies a state-mutating cache operation and that regeneration follows, but it does not say whether invalidation is eager or lazy, whether it touches the IDB or requires a save, or what it costs on a large database.

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?

A single sentence that front-loads the verb and resource with zero filler. Nothing to trim and nothing awkwardly deferred.

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?

For a three-parameter maintenance tool whose schema is fully documented, this is close to sufficient, but with no annotations and no output schema the description should still state whether the call recompiles immediately or merely marks entries stale, which matters for an agent sequencing it before `decompile`.

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%, including the crucial detail that omitting `addresses` clears ALL cached decompilations and the multi-instance `instance_id` requirement, so the schema already does the heavy lifting. The description adds no semantics beyond that baseline.

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 names a specific action (invalidate) on a specific resource (cached Hex-Rays decompilations) and its effect (they are regenerated). It is distinguishable from the sibling `decompile` by making clear this manipulates the cache rather than producing output, though it never names that sibling explicitly.

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 only implied: an agent can infer this is for stale or inconsistent decompiler output, but the description gives no explicit trigger conditions, no prerequisites, and no guidance on when `decompile` should be called instead. Nothing is misleading, but nothing routes the agent either.

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