Skip to main content
Glama

get_local_device

Retrieve local device information for mobile and desktop applications using Frida's dynamic instrumentation capabilities. Supports process management, device control, and runtime analysis.

Instructions

Get the local device.

Returns:
    Information about the local device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler implementation for 'get_local_device'. Directly calls frida.get_local_device() to retrieve and return the local device's id, name, and type, or raises ValueError if not available.
    @mcp.tool()
    def get_local_device() -> Dict[str, Any]:
        """Get the local device.
    
        Returns:
            Information about the local device
        """
        try:
            device = frida.get_local_device()
            return {
                "id": device.id,
                "name": device.name,
                "type": device.type,
            }
        except frida.InvalidArgumentError:  # Or other relevant Frida exceptions
            raise ValueError("No local device found or error accessing it.")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states 'Returns: Information about the local device' without specifying what information is returned, format, potential errors, or any behavioral traits like whether this is a read-only operation, requires permissions, or has rate limits.

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 appropriately concise with two brief sentences that get straight to the point. It's front-loaded with the main purpose and follows with return information. There's no wasted verbiage or unnecessary elaboration.

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 has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally complete. However, for a tool in a context with many sibling device/process tools, it should better differentiate itself and provide more behavioral context since no annotations are present.

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 with 100% schema description coverage, so the schema already fully documents the lack of parameters. The description appropriately doesn't add parameter information beyond what's in the schema, which is correct for a parameterless tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose as 'Get the local device' which is a clear verb+resource combination, but it doesn't differentiate from sibling tools like 'get_device' or 'enumerate_devices'. The description is vague about what 'local device' means in this context compared to other device-related tools.

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 like 'get_device' or 'enumerate_devices'. There's no mention of prerequisites, context, or comparison with sibling tools that handle devices or processes.

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