Skip to main content
Glama
rahulkr

Enhanced ADB MCP Server

by rahulkr
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

set_location

Set GPS coordinates on Android emulators for testing location-based features in development and QA workflows.

Instructions

Set GPS location (works on emulators)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYes
longitudeYes
device_serialNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/adb_mcp_server/server.py:1105-1114 (handler)
    The main handler function for the 'set_location' tool. It is decorated with @mcp.tool(), which likely handles both registration and schema definition via type hints. Executes ADB command to set GPS location on an Android emulator.
    @mcp.tool()
def set_location(
    latitude: float, 
    longitude: float,
    device_serial: str | None = None
) -> str:
    """Set GPS location (works on emulators)"""
    return run_adb([
        "emu", "geo", "fix", str(longitude), str(latitude)
    ], device_serial)

Tool Definition Quality

B3.1/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. While 'Set GPS location' implies a write/mutation operation, the description doesn't address permissions needed, whether changes persist, what happens on physical devices, or error conditions. The emulator note is helpful but insufficient for a mutation tool.

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 (7 words) with zero wasted words. It's front-loaded with the core functionality and includes important qualification about emulator compatibility in parentheses.

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 mutation tool with 3 parameters and no annotations, the description is minimal but covers the essential action. The presence of an output schema means return values don't need explanation. However, more context about the mutation's impact and limitations would be valuable given the tool's nature.

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?

With 0% schema description coverage, the description provides no parameter information beyond what's in the schema. It doesn't explain what latitude/longitude values are expected, what device_serial does, or provide any usage examples. The baseline is 3 since the schema itself documents the parameters adequately.

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 purpose with a specific verb ('Set') and resource ('GPS location'), and adds important context about emulator compatibility. However, it doesn't explicitly differentiate from sibling tools that might also manipulate device settings or location.

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. There are no prerequisites mentioned, no indication of when this operation is appropriate, and no comparison to other location-related tools (though none appear in the sibling list).

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