httptoolkit-mcp

by FL1NEE

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

adb connect

adb_connect

Connect to an Android emulator via TCP using a host:port or a preset name to enable traffic interception and mocking.

Instructions

Connect to an emulator over TCP. Accepts a host:port or a preset name (nox, memu, bluestacks, ldplayer). See list_emulator_presets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": "<target>"
    },
    "name": "adb_connect"
  }
}

Input Schema

Name	Required	Description	Default
`target`	Yes	host:port (e.g. 127.0.0.1:62001) or preset name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 11, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It explains the connection over TCP but does not disclose error handling, authentication needs, or idempotency. This is adequate for a simple operation but lacks depth.

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 sentences long, directly conveys the core functionality, and includes a helpful cross-reference to a related tool. No unnecessary words.

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

Completeness4/5

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

For a tool with one parameter and no output schema, the description is fairly complete. It covers the action, input format, and points to a sibling for presets. However, it could briefly mention the outcome or success indicator.

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?

Schema coverage is 100% with a clear description of the 'target' parameter. The description adds value by providing concrete preset examples (nox, memu, bluestacks, ldplayer) and referencing the presets list, which enhances understanding beyond the schema.

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 tool connects to an emulator over TCP, and distinguishes it from siblings by mentioning host:port or preset names. It directly maps to the tool name and purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a clear context for usage, including accepting host:port or preset names, and directs users to the sibling tool 'list_emulator_presets' for preset options. However, it does not explicitly state when not to use this tool versus other adb_* siblings.

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