Skip to main content
Glama
cbxss
by cbxss

memory_list_exports

List all exported functions from a specified module to examine its APIs and dependencies during Android security analysis.

Instructions

List exports (functions) from a specific module

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
module_nameYesName of the module (e.g., 'libc.so')

Implementation Reference

  • The Python handler function that executes 'memory_list_exports'. It obtains an API handle and calls api.memory_list_exports(module_name) with a timeout, returning the list of exports from the specified module.
    def memory_list_exports(module_name: str) -> list[dict]:
        """List exports from a module."""
        api = get_api()
        return with_timeout(lambda: api.memory_list_exports(module_name))
  • The MCP tool definition/schema for 'memory_list_exports', declaring name, description, and inputSchema requiring 'module_name' as a string property.
    Tool(
        name="memory_list_exports",
        description="List exports (functions) from a specific module",
        inputSchema={
            "type": "object",
            "properties": {
                "module_name": {"type": "string", "description": "Name of the module (e.g., 'libc.so')"},
            },
            "required": ["module_name"],
        },
  • The dispatch/registration point where the tool name 'memory_list_exports' is routed to memory.memory_list_exports(arguments['module_name']).
    elif name == "memory_list_exports":
        return memory.memory_list_exports(arguments["module_name"])
  • The Frida agent-side implementation that actually enumerates exports from a module using Process.findModuleByName() and mod.enumerateExports(), mapping results to name, address, and type.
    memoryListExports(moduleName) {
        const mod = Process.findModuleByName(moduleName);
        if (!mod) return [];
        return mod.enumerateExports().map(e => ({
            name: e.name,
            address: e.address.toString(),
            type: e.type
        }));
    },
Behavior2/5

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

No annotations provided. Description does not disclose behavior beyond listing; e.g., no mention of read-only nature, performance impact, or that it requires a valid module name.

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?

Single sentence, front-loaded with verb and resource, no wasted words.

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?

Simple tool with one parameter and no output schema. Description covers the basic purpose but lacks detail on output format or prerequisites. Adequate but not rich.

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 has 100% coverage with a description for module_name. Description adds no extra meaning beyond 'from a specific module'. Baseline score of 3 applies.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'List exports (functions) from a specific module', clearly identifying the verb 'list' and resource 'exports (functions)'. It distinguishes from siblings like 'memory_list_modules' which lists modules, not exports.

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?

No guidance on when to use this tool vs alternatives. Does not mention prerequisite of listing modules first or that exports are functions.

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/cbxss/frida-mcp'

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