Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Declare Struct

declare_struct

Declares or updates a struct in the local IDA type library, enabling reverse engineers to define and maintain binary data structures during analysis.

Instructions

Declare or update a struct in the local type library.

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": {
      "decl": "<decl>"
    },
    "name": "declare_struct"
  }
}

Input Schema

NameRequiredDescriptionDefault
declYesStruct declaration text (e.g. 'struct Name { ... };')
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

C2.9/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. 'Declare or update' hints at a mutation to the local type library, but nothing is said about whether the change persists without save_database, whether an existing struct is silently overwritten, or whether conflicts produce an error — all critical for an IDA type-library write.

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 tight sentence with zero waste and the verb-resource pair front-loaded. It is efficient but so short that conciseness comes at the cost of the missing behavioral detail noted elsewhere.

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?

No output schema and no annotations, so the description should explain persistence, conflict/overwrite behavior and the result of a failed parse. For a type-definition mutation tool in a family of similar declare_* siblings, the single sentence leaves significant gaps.

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 coverage is 100%, so decl, timeout and instance_id are already documented, including the important multi-instance rule for instance_id. The description adds nothing further, which meets the baseline but does not exceed it.

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?

Specific verb+resource: 'Declare or update a struct in the local type library.' The word 'struct' implicitly separates it from declare_enum, declare_typedef and declare_stack, but the description never states that distinction explicitly, so an agent comparing those four siblings gets no direct disambiguation.

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 versus declare_typedef/declare_enum/declare_stack, no prerequisites, and no mention of what condition (e.g. a pre-existing type name) should route the agent elsewhere. Usage must be inferred entirely from the tool name.

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