Skip to main content
Glama
0xhackerfren

Frida Game Hacking MCP

by 0xhackerfren

unload_script

Remove a custom script from memory to stop its execution and free resources in game hacking or reverse engineering workflows.

Instructions

Unload a custom script.

Args:
    name: Name of the script to unload

Returns:
    Unload status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'unload_script' MCP tool. It unloads a previously loaded custom Frida script by its name from the global session state, removing it from the custom_scripts dictionary after calling unload() on the script object.
    @mcp.tool()
    def unload_script(name: str) -> Dict[str, Any]:
        """
        Unload a custom script.
        
        Args:
            name: Name of the script to unload
        
        Returns:
            Unload status.
        """
        global _session
        
        if name not in _session.custom_scripts:
            return {"error": f"Script '{name}' not found"}
        
        try:
            _session.custom_scripts[name].unload()
            del _session.custom_scripts[name]
            return {"success": True, "name": name}
        
        except Exception as e:
            return {"error": f"Failed to unload script: {str(e)}"}
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but lacks critical behavioral details: whether unloading is reversible, what permissions are needed, if it affects system stability, or what 'Unload status' entails. For a mutation tool with zero annotation coverage, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and structured with Args and Returns sections, making it easy to parse. However, the 'Returns' line is vague ('Unload status') and could be more informative without adding bulk.

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 one parameter, no annotations, and an output schema (which should detail return values), the description is minimally adequate. It covers the basic action but lacks context on effects, alternatives, or error handling, making it incomplete for safe use in a complex sibling environment.

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 description coverage is 0%, but the description adds basic semantics by explaining 'name' refers to the script to unload. However, it doesn't specify format constraints (e.g., case sensitivity, path requirements) or examples, leaving gaps despite the single parameter.

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 'unload' and resource 'custom script', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'detach' or 'unhook_function' that might also remove components, leaving some ambiguity about what specifically distinguishes this tool.

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. With siblings like 'detach', 'unhook_function', and 'remove_breakpoint' that might handle different unloading scenarios, the description offers no context about prerequisites, timing, or comparisons.

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/0xhackerfren/frida-game-hacking-mcp'

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