Skip to main content
Glama
Sign In
Android-MCP

Android-MCP

by HadyAhmed00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Export-Test-Script

Convert recorded Android UI actions into executable test scripts. Choose from Python, pytest, JSON, or readable formats for replay and assertions.

Instructions

Export recorded test actions as executable test script. Supported formats: python (default, simple replay script), pytest (with assertions), json, readable.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "Export-Test-Script"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNopython
filenameNo
test_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add useful output-behavior details such as the python default being a simple replay script and pytest including assertions. However, it does not disclose whether a file is written, whether files can be overwritten, or what the invocation returns.

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, front-loaded sentence with no filler. It conveys the core purpose and format variants compactly.

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?

There is no output schema, and the description does not describe return values, file output behavior, or the effect of the optional filename and test_name parameters. An agent would need to make unsafe assumptions to call this tool correctly.

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. It explains the format parameter and its default, but filename and test_name are left entirely unexplained, both in the schema and in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource construction: 'Export recorded test actions as executable test script.' It names the output type and supported formats, which clearly distinguishes it from sibling recording and interaction tools.

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 establishes the context: this is for recorded test actions, so the agent can infer it should be used after recording rather than during capture. It does not explicitly name alternatives, but no sibling tool fulfills this export role.

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

Deploy Server

Other Tools