Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Rename Local Variable

rename_local_variable

Rename a local variable in an IDA Pro Hex-Rays function by providing its function address, exact old name, and a valid C identifier for the new name.

Instructions

Rename local variable (Hex-Rays).

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": {
      "function_address": "<function_address>",
      "old_name": "<old_name>",
      "new_name": "<new_name>"
    },
    "name": "rename_local_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNoTimeout in seconds
new_nameYesNew variable name (valid C identifier)
old_nameYesOld local variable name (exact match)
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.
function_addressYesFunction start or internal address (hex or decimal)

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

C2.6/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 of behavioral disclosure. It only implies a mutation operation and mentions Hex-Rays, but does not explain side effects, required permissions, error conditions (e.g., invalid or conflicting name), or whether changes are reversible.

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?

The description is extremely short and front-loaded with no wasted words. Its brevity is efficient, though it borders on under-specification rather than being a model of concise completeness.

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?

This is a mutation tool with no annotations and no output schema, yet the description omits important context such as the need for an active Hex-Rays decompilation, expected failure modes, and effects on the decompiler view. The full schema coverage helps with parameters but not with behavioral context.

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 five parameters are already well documented in the schema. The description adds no parameter-level meaning beyond what is structurally provided, which fits the baseline of 3 when schema coverage is high.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 ('Rename local variable') and the '(Hex-Rays)' qualifier identifies the decompiler context. However, it largely restates the tool name and does not explicitly differentiate itself from sibling renaming tools such as rename_global_variable or rename_function.

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?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites such as requiring an active decompilation or open database. The name implies the operation, but the description offers no contextual selection criteria.

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