Skip to main content
Glama
fdciabdul

httptoolkit-mcp

by fdciabdul
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Setup Android Frida Host

frida_android_setup

Set up Frida server on Android via ADB to prepare for app-level HTTP(S) interception and debugging in HTTP Toolkit.

Instructions

Set up a Frida host on an Android device connected via ADB. This prepares the device for app-level interception by installing the Frida server and CA certificate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
proxyPortYesProxy port
hostIdYesFrida host ID. Use get_interceptor_metadata with id "android-frida" to list available hosts.

Implementation Reference

  • src/index.ts:225-237 (handler)
    The 'frida_android_setup' tool registration in src/index.ts. It uses the `client.activateInterceptor` method from `HttpToolkitClient` to perform the setup by passing 'android-frida' as the interceptor ID and { action: 'setup' } in the options.
    server.registerTool(
  'frida_android_setup',
  {
    title: 'Setup Android Frida Host',
    description: 'Set up a Frida host on an Android device connected via ADB. This prepares the device for app-level interception by installing the Frida server and CA certificate.',
    inputSchema: z.object({
      proxyPort: z.number().describe('Proxy port'),
      hostId: z.string().describe('Frida host ID. Use get_interceptor_metadata with id "android-frida" to list available hosts.'),
    }),
  },
  async ({ proxyPort, hostId }) =>
    jsonResult(await client.activateInterceptor('android-frida', proxyPort, { action: 'setup', hostId }))
);

Tool Definition Quality

A3.5/5.0
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 mentions installing components (Frida server and CA certificate) which implies a mutation/write operation, but doesn't disclose permission requirements, whether changes are reversible, potential device impacts, or error handling. This is a significant gap for a setup tool with zero annotation coverage.

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?

Two sentences with zero waste. The first sentence states the core action and target, the second explains the purpose and what gets installed. Every word earns its place with no redundancy or fluff.

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?

For a setup/mutation tool with no annotations and no output schema, the description is adequate but incomplete. It explains what the tool does but lacks information about behavioral traits, return values, error conditions, or dependencies. Given the complexity of device setup operations, more context would be beneficial.

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?

Schema description coverage is 100%, so the schema already documents both parameters. The description doesn't add any parameter-specific information beyond what's in the schema. The baseline score of 3 is appropriate when the schema does the heavy lifting for parameter documentation.

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 specific action ('Set up a Frida host'), target resource ('Android device connected via ADB'), and purpose ('prepares the device for app-level interception by installing the Frida server and CA certificate'). It distinguishes from siblings like frida_android_intercept or frida_android_launch by focusing on setup rather than interception or launching.

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?

The description implies usage context ('prepares the device for app-level interception') but doesn't explicitly state when to use this tool versus alternatives like intercept_android_adb or other Frida tools. It mentions the need for ADB connection but doesn't provide guidance on prerequisites or exclusions.

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/fdciabdul/httptoolkit-mcp'

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