Skip to main content
Glama
0xhackerfren

Frida Game Hacking MCP

by 0xhackerfren

call_rpc

Execute RPC methods from loaded scripts to interact with game processes, enabling remote procedure calls for game hacking and reverse engineering tasks.

Instructions

Call an RPC export from a loaded script.

Args:
    name: Name of the loaded script
    method: RPC method name to call
    args: Arguments to pass

Returns:
    RPC result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
methodYes
argsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'call_rpc' tool. It invokes RPC methods exported by previously loaded custom Frida scripts using script.exports.method(*args). Requires a prior call to load_script.
    @mcp.tool()
    def call_rpc(name: str, method: str, args: List[Any] = None) -> Dict[str, Any]:
        """
        Call an RPC export from a loaded script.
        
        Args:
            name: Name of the loaded script
            method: RPC method name to call
            args: Arguments to pass
        
        Returns:
            RPC result.
        """
        global _session
        
        if name not in _session.custom_scripts:
            return {"error": f"Script '{name}' not found"}
        
        try:
            script = _session.custom_scripts[name]
            rpc_method = getattr(script.exports, method)
            result = rpc_method(*(args or []))
            return {"success": True, "method": method, "result": result}
        
        except AttributeError:
            return {"error": f"RPC method '{method}' not found"}
        except Exception as e:
            return {"error": f"RPC call failed: {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 the full burden of behavioral disclosure. It mentions 'Call an RPC export' but doesn't explain what happens during the call (e.g., whether it blocks, error handling, permissions needed, or side effects). This is a significant gap for a tool that likely involves execution in a potentially sensitive context.

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 appropriately sized and front-loaded, with a clear purpose statement followed by concise sections for 'Args' and 'Returns'. Every sentence earns its place, and there's no wasted text, making it easy to scan and understand quickly.

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 (executing RPC calls in a script context) and the presence of an output schema (which handles return values), the description is moderately complete. It covers the basic purpose and parameters but lacks details on behavioral aspects like error handling or dependencies, which are important for safe usage in this domain.

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 description adds meaningful context for all three parameters ('name', 'method', 'args') beyond the input schema, which has 0% description coverage. It explains that 'name' refers to a loaded script, 'method' is the RPC method to call, and 'args' are arguments to pass. This compensates well for the lack of schema descriptions, though it doesn't detail argument formats or constraints.

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: 'Call an RPC export from a loaded script.' It specifies the verb ('Call') and resource ('RPC export from a loaded script'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'load_script' or 'unload_script', which handle script management rather than execution.

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 prerequisites (e.g., needing a script loaded first), exclusions, or comparisons to sibling tools like 'hook_function' or 'replace_function' for other execution methods. Usage is implied but not explicitly stated.

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