Skip to main content
Glama
Sign In
IDA-MCP

IDA-MCP

by Captain-AI-Hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Function Signature

get_function_signature

Retrieves the available function signature string for a given address or name, with optional timeout and instance ID for multi-IDA Pro sessions.

Instructions

Get the best available function signature string.

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": {
      "addr": "<addr>"
    },
    "name": "get_function_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
addrYesFunction address or 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.5/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 behavioral burden, and it discloses almost nothing beyond an implied read-only 'get'. It does not explain what 'best available' means, whether the function must be analyzed first, what the returned string format looks like, or how instance_id requirements affect behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no waste, but it is under-specified rather than effectively concise. The most important qualifier, 'best available', is left unexplained, so brevity comes at the cost of clarity.

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 a three-parameter tool with no annotations and no output schema, the description is too thin. It does not explain the return value format, what 'best available' resolution means, or how this differs from the signature-making tools, leaving meaningful gaps for an agent to navigate.

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%, and the schema itself contains useful parameter descriptions, including a substantial note on when instance_id is required. The tool description adds no parameter meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 names a specific verb and resource ('Get ... function signature string'), so the basic purpose is clear. However, 'best available' is vague about where the signature comes from (debug info, type inference, name only), and it does not distinguish this from siblings like make_signature, make_signature_for_function, or make_signature_for_range.

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 retrieval tool versus the signature-making siblings, nor any mention of prerequisites or error conditions. The agent is left to infer usage entirely from the 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