Skip to main content
Glama
jegriffi91

Mobile Automator MCP Server

by jegriffi91

Stop and Compile Test

stop_and_compile_test
Idempotent

Stop the active recording and synthesize a Maestro YAML test script that captures UI interactions, network payloads, and analytics assertions.

Instructions

Stop the active recording session and synthesize a Maestro YAML test script. Correlates captured UI interactions with network payloads and embeds JavaScript assertions for analytics events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesThe session ID returned by start_recording_session
conditionsNoOptional natural-language assertions to include, e.g. "verify analytics event: page_view"
outputPathNoAbsolute path where the generated .yaml file should be written
mockingConfigNoNetwork mocking configuration for WireMock stub generation

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yamlYesThe generated Maestro YAML test script content
stubsDirNoWireMock stubs root directory containing mappings/ and __files/ subdirectories
yamlPathYesFile path where the YAML was written
sessionIdYesThe session that was compiled
fixturesDirNoDirectory containing WireMock response fixtures
manifestPathNoPath to the session manifest JSON
timelinePathNoPath to the session timeline JSON file for post-hoc debugging
flowExecutionsNoPhase 5: per-flow summary for run_test / run_flow executions captured mid-session. The full step stream lives in the timeline.json file.
matchedSegmentsNoExisting registered segments that match this recording
pollingDiagnosticsNoHealth diagnostics from the passive capture polling loop
segmentFingerprintNoSHA-256 fingerprint of the action+endpoint sequence for deduplication
Behavior3/5

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

Annotations already indicate idempotent and non-destructive. The description adds that it correlates UI and network data and embeds assertions, but does not explain session termination side effects or prerequisites.

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, front-loading the core action in the first clause, and provides meaningful detail in a second sentence. No wasted words.

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?

The description covers the core functionality but lacks usage context, prerequisites, and side effects. Given the complexity (nested parameters, output schema exists), more guidance is beneficial.

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?

Schema coverage is 100%, so parameters are well-documented in the schema. The description adds no additional parameter insight beyond what the schema provides.

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 stops a recording session and synthesizes a test script, using specific verbs and resource types. It is not explicitly differentiated from siblings like run_feature_test, but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternatives guidance is provided. The context implies it follows start_recording_session, but this is not stated.

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/jegriffi91/mobile-automator-mcp'

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