Skip to main content
Glama

get_function_definition

Retrieve function details by name to analyze binary code structure and behavior for reverse-engineering tasks.

Instructions

Get details of a specific function definition by name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • main.py:126-133 (handler)
    Handler function that retrieves the details of a specific function definition by name from the loaded Ghidra context JSON. Returns the definition dict or an error.
    async def get_function_definition(name: str) -> dict:
        """Get details of a specific function definition by name."""
        if not ctx_ready:
            return {"error": "Context not ready. Run `setup_context()` first."}
        for f in ctx.get("data_types", {}).get("function_definitions", []):
            if f["name"] == name:
                return f
        return {"error": f"Function definition '{name}' not found."}
  • main.py:125-125 (registration)
    Registers the get_function_definition tool with the MCP server using the @mcp.tool() decorator.
    @mcp.tool()
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 it 'gets details' but doesn't specify what details are returned, whether it's a read-only operation, error handling, or any constraints. This leaves significant gaps for a tool with unknown behavior.

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 that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain what 'details' are returned, how to handle errors, or provide context for the single parameter, making it insufficient for effective tool use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions the parameter 'name' but doesn't add meaning beyond what the schema's title 'Name' implies, such as format, examples, or scope. With 1 undocumented parameter, this is inadequate compensation.

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 ('Get details') and resource ('specific function definition by name'), making the purpose understandable. However, it doesn't differentiate this tool from similar siblings like 'get_enum', 'get_structure', or 'list_function_definitions' beyond specifying it's for function definitions.

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 is provided on when to use this tool versus alternatives like 'list_function_definitions' or 'get_pseudocode'. The description implies usage for retrieving details of a known function by name, but lacks explicit context, prerequisites, or exclusions.

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