Skip to main content
Glama

android_connect

Destructive

Connect an already-paired Android phone over ADB using its host:port address, then inspect available devices to confirm the connection.

Instructions

Connect an already-paired phone using its CONNECTION host:port. Does not change the selected phone. Inspect android_devices afterwards.

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": {
      "address": "<address>"
    },
    "name": "android_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true and idempotentHint=false. The description adds two facts the annotations do not: the connection does not alter the currently selected device, and the resulting state should be verified via android_devices — meaningful context for a destructive, non-idempotent network operation, though it does not explain what makes it destructive.

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?

Three short sentences, each carrying distinct information: the action, the state side effect, and the verification step. Nothing is padded or repeated.

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 one-parameter tool with no output schema, the description covers the input format, the state implications, and how to confirm results. The main remaining gap is what the call returns or fails with, which the pointer to android_devices partially mitigates.

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 description coverage is 0% and the single parameter only has a regex pattern. The phrase "using its CONNECTION host:port" supplies the format semantics (host plus port from the device's connection string) that the schema itself does not convey.

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 uses a specific verb and resource ("Connect an already-paired phone") and scopes it to the CONNECTION host:port address. "Already-paired" implicitly distinguishes it from android_pair, and "Does not change the selected phone" distinguishes it from android_select_device, though neither sibling is named explicitly.

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?

It states the precondition (device must already be paired) and the follow-up action ("Inspect android_devices afterwards"), which tells the agent when and how to use it. It stops short of naming android_pair as the alternative for unpaired devices, so routing relies on inference.

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