Skip to main content
Glama
fuzzmind

fuzzmind-frida-mcp

by fuzzmind

frida_android_frida_server_setup

Installs, starts, and optionally forwards a user-supplied frida-server binary to an Android device via ADB, enabling Frida dynamic analysis.

Instructions

Install, start, and optionally forward to a user-supplied frida-server binary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_binary_pathYes
adb_serialNo
remote_pathNo/data/local/tmp/frida-server
as_rootNo
forwardNo
local_portNo
remote_portNo
Behavior2/5

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

No annotations provided, and the description does not disclose side effects like overwriting, error conditions, or behavior if server already running. Only mentions actions without detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise but excessively sparse given tool complexity. Lacks structured details.

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

Completeness1/5

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

Highly incomplete for a 7-parameter tool with no output schema. No explanation of return values, parameter meanings, or relation to sibling tools.

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

Parameters1/5

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

Schema coverage 0% and description does not explain any of the 7 parameters. The bare mention of 'user-supplied frida-server binary' adds minimal value.

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

Purpose5/5

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

The description clearly states the verb (install, start, forward) and resource (frida-server binary). It distinguishes from siblings like frida_android_frida_server_install and frida_android_frida_server_start by combining these actions.

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?

No guidance on when to use this combined tool versus the individual install/start/forward tools. No prerequisites or context provided.

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/fuzzmind/frida-mcp'

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