Skip to main content
Glama

configure_remote_device

Connect to a remote Frida server for dynamic instrumentation, enabling runtime analysis and reverse engineering of mobile and desktop applications.

Instructions

Connect to a remote Frida server and make it available for future requests.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe remote <host>:<port> to add.
aliasNoOptional alias used as device_id when targeting this remote.
set_as_defaultNoIf true, future requests without device_id will prefer this remote.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The @mcp.tool()-decorated handler function implementing the 'configure_remote_device' tool. Defines input schema via pydantic Fields and delegates core logic to register_remote_device helper.
    @mcp.tool()
    def configure_remote_device(
        address: str = Field(description="The remote <host>:<port> to add."),
        alias: Optional[str] = Field(
            default=None,
            description="Optional alias used as device_id when targeting this remote.",
        ),
        set_as_default: bool = Field(
            default=False,
            description="If true, future requests without device_id will prefer this remote.",
        ),
    ) -> Dict[str, Any]:
        """Connect to a remote Frida server and make it available for future requests."""
    
        try:
            info = register_remote_device(address, alias=alias, set_default=set_as_default)
        except DeviceSelectionError as exc:
            if exc.reasons:
                attempts = "; ".join(exc.reasons)
                raise ValueError(f"{exc}. Attempts: {attempts}") from exc
            raise ValueError(str(exc)) from exc
    
        response: Dict[str, Any] = {"status": "success"}
        response.update(info)
        if set_as_default:
            response["message"] = "Remote device set as default"
        return response
  • Helper function called by the tool handler. Uses DeviceSelector to register the remote device, cache it, and return device info including alias and default status.
    def register_remote_device(
        address: str,
        *,
        alias: Optional[str] = None,
        set_default: bool = False,
    ) -> Dict[str, str]:
        """Register a remote device using the active selector."""
    
        global _selector
        if _selector is None:
            _selector = DeviceSelector()
    
        device = _selector.register_remote(address, alias=alias, set_default=set_default)
        normalized = _normalize_remote_identifier(address)
        resolved_alias = _selector._config.alias_for_address(normalized)
        return {
            "id": device.id,
            "name": device.name,
            "type": device.type,
            "address": normalized,
            "alias": resolved_alias or normalized,
            "default_remote": _selector._config.default_remote or "",
        }
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 the tool connects to a remote server and makes it available for future requests, which implies a persistent configuration change. However, it lacks details on authentication requirements, error handling (e.g., if the server is unreachable), side effects, or how this interacts with other tools. The description is minimal and doesn't compensate for the absence of annotations.

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. It's front-loaded with the core action ('Connect to a remote Frida server') and follows with the outcome ('make it available for future requests'). There's no wasted verbiage or redundancy.

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 that there's an output schema (not provided in details but indicated as present), the description doesn't need to explain return values. However, for a configuration tool with no annotations and three parameters, the description is minimal. It covers the basic purpose but lacks context on behavioral traits, usage guidelines, or integration with sibling tools. It's adequate as a starting point but has clear gaps in completeness.

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?

The input schema has 100% description coverage, providing clear documentation for all three parameters (address, alias, set_as_default). The description adds no additional parameter semantics beyond what's in the schema. According to the rules, with high schema coverage (>80%), the baseline score is 3 when no param info is added in the description.

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: 'Connect to a remote Frida server and make it available for future requests.' It specifies the verb ('connect') and resource ('remote Frida server'), and indicates a persistent effect ('available for future requests'). However, it doesn't explicitly differentiate from sibling tools like 'get_local_device' or 'get_usb_device' which might handle different device types.

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 running Frida server), exclusions (e.g., not for local devices), or comparisons to siblings like 'enumerate_devices' or 'get_device'. Usage context 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/rmorgans/frida-mcp'

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