Skip to main content
Glama
Sign In
Android-MCP

Android-MCP

by HadyAhmed00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Clear-Recording-Tool

Remove all recorded test actions from an Android testing session to reset the environment and prepare for a clean automation run.

Instructions

Clear all recorded test actions

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": "Clear-Recording-Tool"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/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 that the tool clears recorded actions, implying a destructive operation, but does not mention whether this action is irreversible, whether it also stops recording, or whether any confirmation is required. This is a significant gap for a potentially destructive 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 a single, compact sentence with no wasted words. The verb and object are front-loaded, and every word contributes to meaning.

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 tool is simple (no parameters, no output schema), so a short description can be adequate. However, the absence of any behavioral caveats (e.g., irreversibility, effect on current recording session) leaves the agent without context that is typically important for a clearing/reset operation. A slightly expanded description would be more complete.

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

Parameters4/5

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

The tool has zero parameters and the input schema covers 100% of the parameter space, so the baseline is 4. The description correctly adds no parameter details because there are none to explain.

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 states a specific verb ('Clear') and a specific resource ('all recorded test actions'), making the tool's purpose immediately obvious. It is distinct from sibling tools like Start-Recording-Tool, Stop-Recording-Tool, and Export-Test-Script, which perform different operations on the same recording context.

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?

No guidance is provided about when to use this tool versus its siblings. The description does not mention prerequisites, whether clearing affects an ongoing recording, or any scenario where an alternative tool such as Stop-Recording-Tool or Get-Recording-Stats-Tool would be more appropriate.

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