@wilsonbeam/openclaw-adb-mcp

by wilsonbeam

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

adb_make_call

Place an immediate phone call to a given number using ADB. Provide the phone number to dial instantly.

Instructions

Make a phone call to the specified number (dials immediately)

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": {
      "phoneNumber": "<phoneNumber>"
    },
    "name": "adb_make_call"
  }
}

Input Schema

Name	Required	Description	Default
`deviceId`	No	Target device ID (optional)
`phoneNumber`	Yes	Phone number to call (can include +, spaces, dashes)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the call 'dials immediately,' but fails to mention potential side effects (e.g., ending an active call), permissions required, or whether the action is reversible. This is a significant gap for a side-effectful operation.

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 a single, clear sentence with a parenthetical for emphasis. It is concise and front-loaded, with no wasted words.

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?

The tool performs a significant, state-changing action, yet the description is minimal. It lacks information about return values, failure modes, whether the action blocks, or how it interacts with other call-related tools (e.g., adb_call_state). Given no output schema and no annotations, this is incomplete for an action of this complexity.

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?

The input schema already provides 100% coverage for both parameters (phoneNumber, deviceId) with clear descriptions. The description adds no further parameter semantics beyond 'specified number,' which maps directly to phoneNumber. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the tool's action ('Make a phone call') and resource ('specified number'), with an added behavioral detail ('dials immediately'). It is specific and unambiguous, though it does not explicitly differentiate from sibling adb_dial_number, which might appear similar.

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?

The description provides no guidance on when to use this tool versus alternatives like adb_dial_number or adb_start_activity. It does not mention prerequisites, context, or exclusions, leaving the agent without direction for tool selection.

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