Skip to main content
Glama

get_structure

Extract structure details from binary files by name to analyze data layouts in reverse engineering workflows.

Instructions

Get details of a specific structure by name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • main.py:91-99 (handler)
    The handler function for the 'get_structure' tool. It retrieves the details of a specific structure by name from the Ghidra context loaded via setup_context. Registered using the @mcp.tool() decorator.
    @mcp.tool()
    async def get_structure(name: str) -> dict:
        """Get details of a specific structure by name."""
        if not ctx_ready:
            return {"error": "Context not ready. Run `setup_context()` first."}
        for s in ctx.get("data_types", {}).get("structures", []):
            if s["name"] == name:
                return s
        return {"error": f"Structure '{name}' not found."}
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 this is a read operation ('Get details'), which implies it's non-destructive, but doesn't address permissions, rate limits, error handling, or what 'details' include. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 function without unnecessary words. It's appropriately sized for a simple lookup tool and front-loads the core purpose effectively.

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, error cases (e.g., invalid name), or how this fits with sibling tools. For a tool in this context, more guidance is needed to help an agent use it correctly.

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' and implies it's used to identify a specific structure, but doesn't explain format constraints, valid values, or how it relates to other tools (e.g., if names come from 'list_structures'). This adds minimal semantic value beyond the bare schema.

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 details') and resource ('specific structure by name'), making the purpose unambiguous. However, it doesn't differentiate this tool from its sibling 'list_structures', which might also retrieve structure information but in a list format rather than by specific name.

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 like 'list_structures' or other sibling tools. It doesn't mention prerequisites, error conditions, or contextual constraints, leaving the agent with minimal usage direction beyond the basic operation.

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