Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set Op Type

set_op_type

Set instruction operand display type to hex, decimal, octal, binary, char, or stack variable for clearer reverse engineering analysis.

Instructions

Set the display type of an instruction operand (hex/dec/oct/bin/char/stkvar).

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": {
      "items": "<items>"
    },
    "name": "set_op_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesList of {address, type, operand?} objects; type: hex|dec|oct|bin|char|stkvar
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 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

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and doesn't. It doesn't say this is a mutating operation, whether the change is persistent/saved with the database, that 'items' is a batch of edits applied together, or that it needs a live instance. The schema note about instance_id being required with multiple databases is the only behavioral hint, and it lives in the schema, not the description.

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?

One front-loaded sentence with no waste. It's efficient but so terse that brevity shades into under-specification rather than optimal conciseness.

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?

For an unannotated mutation tool with no output schema, the description omits batch semantics, persistence of the change, and any precondition like an open database—information an agent needs to call it safely. The 100% schema coverage covers parameter shapes but not 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 the schema already documents items, timeout, and the instance_id requirement, and the description only repeats the type enum. Baseline 3 applies since the description adds no param meaning beyond structured data.

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?

States a specific verb+resource (set the display type of an instruction operand) and enumerates the allowed type values, so an agent can tell what it does and that it's distinct from renaming/typing siblings like set_local_variable_type. It stops short of naming which sibling handles related-but-different tasks.

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: the type list hints at formatting operands, but there's no explicit 'use when you want operands shown as hex/char/etc.' nor any exclusions or prerequisites (e.g., a loaded database, a valid address). An agent must infer the when-to-use from the title and schema.

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