Skip to main content
Glama
0xhackerfren

Frida Game Hacking MCP

by 0xhackerfren

list_capabilities

Discover available game hacking tools for memory scanning, value modification, pattern matching, function hooking, and code injection across processes.

Instructions

List all tools provided by this MCP server.

Returns:
    Dictionary with MCP info and available tools organized by category.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the list_capabilities tool. This handler function returns a dictionary containing the MCP server name, version, description, availability of Frida and screenshot features, categorized lists of available tools, and total tool count.
    @mcp.tool()
    def list_capabilities() -> Dict[str, Any]:
        """
        List all tools provided by this MCP server.
        
        Returns:
            Dictionary with MCP info and available tools organized by category.
        """
        return {
            "mcp_name": "frida-game-hacking-mcp",
            "version": "1.1.0",
            "description": "Cheat Engine-like game hacking capabilities through Frida",
            "frida_available": FRIDA_AVAILABLE,
            "screenshot_available": SCREENSHOT_AVAILABLE,
            "tool_categories": {
                "process_management": [
                    "list_processes", "attach", "detach", "spawn", "resume", "get_session_info"
                ],
                "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
        }
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists tools and returns a dictionary with MCP info and categorized tools, which is useful. However, it lacks details on potential side effects, error conditions, or performance aspects (e.g., if it's a heavy operation). The description doesn't contradict any annotations, but it's minimal for a tool with no annotation support.

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 and well-structured: two sentences that directly state the purpose and return value. Every word earns its place, with no redundancy or fluff. It's front-loaded with the main action, making it easy to understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 annotations, but has an output schema), the description is reasonably complete. It explains what the tool does and what it returns, and since an output schema exists, it doesn't need to detail return values further. However, it could improve by adding usage context or behavioral nuances, but for a basic listing tool, it's adequate.

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 semantics, as there are none to explain. This meets the baseline for tools with no parameters, as it doesn't mislead or omit necessary details about inputs.

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 tool's purpose: 'List all tools provided by this MCP server.' It specifies the verb ('List') and resource ('tools provided by this MCP server'), making the action clear. However, it doesn't explicitly differentiate from sibling tools like 'get_session_info' or 'list_processes', which might also provide listings but of different resources.

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 any context, prerequisites, or exclusions for usage. Given the many sibling tools, such as 'list_modules' or 'list_processes', there's no indication of when this tool is preferred over others for listing-related tasks.

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