Skip to main content
Glama

List Frida Devices

list_frida_devices
Idempotent

Lists Frida devices available to the host, optionally connecting to a caller-selected remote endpoint with one-time authentication for device discovery.

Instructions

List Frida devices currently available to this host, optionally connecting to the caller-selected remote Frida endpoint. Remote authentication options are used for this call only and are never returned or recorded.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_frida_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
remoteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior1/5

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

The description frames the tool as a listing operation and says remote authentication options are 'used for this call only and are never returned or recorded,' implying no persistent side effects. That conflicts with the annotation readOnlyHint=false, which tells an agent the tool is not read-only. The useful security note is overwhelmed by this contradiction.

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 two short sentences, front-loads the core list operation, and includes the remote-auth caveat without filler. Every sentence contributes directly to the tool's purpose or behavior.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with a nested remote configuration and no output schema, the description does not explain how to populate the remote object or what the returned device list looks like. It also leaves the readOnlyHint inconsistency unresolved, so an agent lacks enough context to use the remote path confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one optional nested remote object with zero schema description coverage aside from keepalive_interval. The description adds only the ideas of a 'remote Frida endpoint' and 'authentication options'; it does not explain address, token, origin, certificate, keepalive_interval, or that address is required within the remote object.

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 states a specific verb and resource: 'List Frida devices currently available to this host.' The host scope and optional remote endpoint are clear, and the resource is distinguishable from sibling tools such as list_frida_processes and list_adb_devices, even though no alternative is explicitly named.

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?

Usage is implied: call this to enumerate Frida devices, optionally against a remote endpoint. However, it does not say when to use this tool versus list_adb_devices or list_frida_processes, nor when omitting the remote parameter is preferable to supplying one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools