Skip to main content
Glama
0xhackerfren

Frida Game Hacking MCP

by 0xhackerfren

clear_scan

Reset scan results and state in Frida Game Hacking MCP to prepare for new memory analysis operations.

Instructions

Clear current scan results and reset scan state.

Returns:
    Confirmation message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'clear_scan' MCP tool. It resets the global FridaSession's scan_state by assigning a new empty ScanState instance and returns a success message.
    def clear_scan() -> Dict[str, Any]:
        """
        Clear current scan results and reset scan state.
        
        Returns:
            Confirmation message.
        """
        global _session
        _session.scan_state = ScanState()
        return {"success": True, "message": "Scan state cleared."}
  • Dataclass defining the ScanState used by the scanning tools, including clear_scan. It holds value_type, results list, last_values dict, and scan_active flag.
    class ScanState:
        """Tracks memory scan state for Cheat Engine-style scanning."""
        value_type: str = ""
        results: List[int] = field(default_factory=list)
        last_values: Dict[int, Any] = field(default_factory=dict)
        scan_active: bool = False
  • The list_capabilities tool lists 'clear_scan' under memory_operations category, confirming its registration in the MCP server.
            "memory_operations": [
                "read_memory", "write_memory", "scan_value", "scan_next",
                "scan_changed", "scan_unchanged", "scan_pattern",
                "get_scan_results", "clear_scan", "list_memory_regions"
            ],
            "module_information": [
                "list_modules", "get_module_info", "get_module_exports",
                "get_module_imports", "resolve_symbol"
            ],
            "function_hooking": [
                "hook_function", "unhook_function", "replace_function",
                "hook_native_function", "list_hooks", "intercept_module_function"
            ],
            "debugging": [
                "set_breakpoint", "remove_breakpoint", "list_breakpoints", "read_registers"
            ],
            "script_management": [
                "load_script", "unload_script", "call_rpc"
            ],
            "window_interaction": [
                "list_windows", "screenshot_window", "screenshot_screen",
                "send_key_to_window", "focus_window"
            ],
            "standard": [
                "list_capabilities", "get_documentation", "check_installation"
            ]
        },
        "total_tools": 42
    }
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 tool clears results and resets state, but doesn't disclose behavioral traits like whether this is destructive (likely yes, but not confirmed), if it requires specific permissions, or what happens to ongoing scans. The mention of a return value is minimal.

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 extremely concise with two sentences: one stating the action and one noting the return value. It's front-loaded with the core purpose and wastes no words, making it highly efficient.

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 complexity (simple reset operation), 0 parameters, 100% schema coverage, and presence of an output schema, the description is minimally complete. However, it lacks details on behavioral aspects (e.g., destructiveness, side effects) that would be helpful for an agent, especially without annotations.

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 schema description coverage is 100%, so no parameter information is needed. The description appropriately doesn't discuss parameters, earning a high baseline score for this dimension.

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?

The description clearly states the tool's purpose with specific verbs ('clear', 'reset') and resources ('current scan results', 'scan state'), distinguishing it from siblings like 'get_scan_results' (which retrieves results) and 'scan_*' tools (which perform scans).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when scan results need to be cleared, but provides no explicit guidance on when to use this versus alternatives (e.g., after a scan is complete, before starting a new scan) or any prerequisites. It's adequate but lacks detailed context.

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