Skip to main content
Glama

list_functions

Extract function names from a loaded binary to identify executable components for reverse-engineering analysis.

Instructions

List all function names from the loaded binary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:67-72 (handler)
    The core handler function for the 'list_functions' tool. It checks if the Ghidra context is ready and returns a list of function names from the loaded binary context.
    @mcp.tool()
    async def list_functions() -> list[str]:
        """List all function names from the loaded binary."""
        if not ctx_ready:
            return ["❌ Context not ready. Run `setup_context()` first."]
        return [f["name"] for f in ctx.get("functions", [])]
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists function names but doesn't describe the return format (e.g., array of strings, pagination), performance characteristics (e.g., speed, memory usage), or any constraints (e.g., binary must be loaded, may be read-only). This leaves significant gaps for an agent to understand how the tool behaves.

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, clear sentence that efficiently conveys the core functionality without unnecessary words. It's front-loaded with the essential action and resource, making it easy to parse quickly.

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, no annotations), the description is minimally adequate but incomplete. It lacks behavioral details (e.g., return format, prerequisites) and usage context compared to siblings, which are important for an agent to operate effectively in this server environment.

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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, so it appropriately focuses on the tool's purpose. A baseline of 4 is justified since no parameters exist to document.

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 action ('List') and resource ('function names from the loaded binary'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its siblings like 'list_function_definitions' or 'get_function_definition', which likely provide more detailed function information rather than just names.

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 prerequisites (e.g., whether a binary must be loaded first), compare it to siblings like 'list_function_definitions' for more details, or specify use cases (e.g., for quick overview vs. in-depth analysis).

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/Bamimore-Tomi/ghidra_mcp'

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