Skip to main content
Glama

get_exports

Retrieve exported functions and symbols from binary files for reverse engineering analysis in IDA Pro.

Instructions

Get list of exports from the binary

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler for the 'get_exports' MCP tool. Validates input arguments, calls ida.getExports() to fetch exports, formats the response as text content with JSON-stringified exports list, or returns an error.
    case 'get_exports':
        if (!isValidGetExportsArgs(request.params.arguments)) {
            throw new McpError(
                ErrorCode.InvalidParams,
                'Invalid get exports arguments'
            );
        }
    
        try {
            const result = await ida.getExports();
    
            return {
                content: [
                    {
                        type: 'text',
                        text: `Retrieved ${result.count} exports from the binary:\n\n${JSON.stringify(result.exports, null, 2)
                            }`,
                    },
                ],
            };
        } catch (error: any) {
            return {
                content: [
                    {
                        type: 'text',
                        text: `Error getting exports: ${error.message || error}`,
                    },
                ],
                isError: true,
            };
        }
  • index.ts:341-349 (registration)
    Tool registration in the ListToolsRequestHandler. Defines the tool name 'get_exports', its description, and empty input JSON schema (no parameters required).
    {
        name: 'get_exports',
        description: 'Get list of exports from the binary',
        inputSchema: {
            type: 'object',
            properties: {},
            required: [],
        },
    },
  • TypeScript interface for GetExportsArgs, indicating no parameters are required for the tool.
    interface GetExportsArgs {
        // No parameters required
    }
  • Type guard function to validate input arguments conform to GetExportsArgs (non-null object).
    const isValidGetExportsArgs = (args: any): args is GetExportsArgs => {
        return (
            typeof args === 'object' &&
            args !== null
        );
    };
  • Core helper method in IDARemoteClient that implements getExports by making a GET request to the IDA Pro remote API endpoint '/exports', returning ExportsResponse.
    async getExports(): Promise<ExportsResponse> {
        return this.get<ExportsResponse>('/exports');
    }
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. It states the action ('Get list') but lacks behavioral details: it doesn't specify if this is a read-only operation, what format the list returns (e.g., structured data, raw text), whether it's paginated or rate-limited, or if it requires specific binary states (e.g., loaded analysis). For a tool with zero annotation coverage, this is a significant gap.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse. No extraneous information is included, which is ideal for a simple tool.

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?

Given the tool's simplicity (0 parameters, no output schema), the description is minimally adequate. It states what the tool does but lacks context about what 'exports' are, the return format, or behavioral traits. Without annotations or output schema, the agent might struggle to use this effectively in complex scenarios, but it's sufficient for basic understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details beyond the schema, but since there are no parameters, the baseline is 4. It appropriately avoids unnecessary parameter explanations.

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 clearly states the verb ('Get') and resource ('list of exports from the binary'), making the purpose understandable. It distinguishes this tool from siblings like 'get_functions' or 'get_strings' by specifying 'exports' as the target resource. However, it doesn't explicitly differentiate from all siblings (e.g., 'get_xrefs_from' also retrieves data from the binary).

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention what 'exports' are in this context (e.g., exported functions, symbols), when this tool is appropriate compared to other 'get_' tools, or any prerequisites. The agent must infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fdrechsler/mcp-server-idapro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server