Skip to main content
Glama
rahulkr

Enhanced ADB MCP Server

by rahulkr
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

toggle_color_inversion

Enable or disable color inversion on Android devices to test accessibility features or simulate different visual conditions for UI development.

Instructions

Enable or disable display color inversion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enableYes
device_serialNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/adb_mcp_server/server.py:1092-1098 (handler)
    Handler function for the 'toggle_color_inversion' tool. It uses ADB to set the accessibility_display_inversion_enabled setting to 1 or 0 based on the enable parameter. Registered via @mcp.tool() decorator.
    @mcp.tool()
def toggle_color_inversion(enable: bool, device_serial: str | None = None) -> str:
    """Enable or disable display color inversion"""
    value = "1" if enable else "0"
    return run_adb([
        "shell", "settings", "put", "secure", "accessibility_display_inversion_enabled", value
    ], 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 the full burden of behavioral disclosure. It states the action but doesn't reveal whether this requires specific permissions, affects device state persistently, has side effects, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap.

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, efficient sentence with zero waste. It's appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

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?

Given the tool's moderate complexity (mutation with 2 parameters), no annotations, and an output schema (which reduces need to describe returns), the description is minimally adequate. It states what the tool does but lacks behavioral context and usage guidance, making it incomplete for optimal agent operation.

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 description doesn't mention any parameters, and schema description coverage is 0%, so the schema provides all parameter documentation. The description doesn't add meaning beyond the schema, but with 2 parameters (one required), the baseline is 3 as the schema handles 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 action ('Enable or disable') and the resource ('display color inversion'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'toggle_high_contrast' or 'toggle_show_layout_bounds' that also toggle display settings, which prevents 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 provides no guidance on when to use this tool versus alternatives like 'toggle_high_contrast' or other display-related tools. There's no mention of prerequisites, context, or exclusions, leaving the agent with minimal usage direction.

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