Skip to main content
Glama
rahulkr

Enhanced ADB MCP Server

by rahulkr
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

simulate_call

Simulate incoming calls on Android emulators to test call handling functionality during development and UI testing workflows.

Instructions

Simulate incoming call (emulator only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phone_numberYes
device_serialNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/adb_mcp_server/server.py:1129-1135 (handler)
    The core handler function for the 'simulate_call' MCP tool. Decorated with @mcp.tool() which handles registration and schema inference from type hints and docstring. Executes ADB command to simulate an incoming phone call on an Android emulator.
    @mcp.tool()
def simulate_call(
    phone_number: str,
    device_serial: str | None = None
) -> str:
    """Simulate incoming call (emulator only)"""
    return run_adb(["emu", "gsm", "call", phone_number], device_serial)

Tool Definition Quality

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool is for emulation only, which is useful context, but fails to describe what the simulation entails (e.g., does it trigger app behaviors, require specific setups, or have side effects like notifications). For a tool that likely interacts with device state, this is insufficient.

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 extremely concise with a single, front-loaded sentence that wastes no words. Every part ('simulate incoming call' and 'emulator only') earns its place by conveying essential information without redundancy.

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?

Given the complexity of a simulation tool with no annotations, 0% schema coverage, and an output schema (which might help but isn't described), the description is incomplete. It lacks details on parameters, behavioral outcomes, error conditions, and how it fits with sibling tools, making it inadequate for safe and effective use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate by explaining parameters. It does not mention 'phone_number' or 'device_serial' at all, leaving both parameters undocumented. The description adds no meaning beyond the schema, failing to clarify what these inputs represent or how they affect the simulation.

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 action ('simulate incoming call') and specifies the environment ('emulator only'), which distinguishes it from real device operations. However, it doesn't explicitly differentiate from sibling tools like 'send_sms' or other communication-related tools, keeping it from a perfect score.

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 includes 'emulator only', which provides some context on when to use it (in emulation environments), but offers no guidance on when not to use it (e.g., on real devices) or alternatives for real device testing. There's no mention of prerequisites or comparison with sibling tools.

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/rahulkr/r_adb_mcp_server'

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