Skip to main content
Glama
Sign In
waydroid-mcp

waydroid-mcp

by TechyAditya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

record_screen

Read-only

Captures a Waydroid display or app window to an MP4 for a fixed duration and returns the saved host file path.

Instructions

Records a display to an MP4 file on the host for a fixed time, then returns its path.

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": "record_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageNoApp to act on. An app in its own window or hidden display is found by package; otherwise Waydroid's main display is used.
display_idNoAndroid display id instead of a package; 0 is Waydroid's main display.
duration_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and does add useful behavior: output is an MP4 written on the host, the capture is time-bounded, and the call returns the file path. It omits whether the call blocks for the whole duration, where on the host the file lands, whether files are overwritten or uniquely named, and any size or permission constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is arguably too terse rather than too verbose, but every word earns its place and the key facts (artifact, location, bounded duration, returned path) come first.

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 three-parameter capture tool with no output schema and minimal annotations, the description covers the artifact and return value adequately. It is not complete enough on duration limits, blocking behavior, and package-versus-display selection, which are exactly what an agent needs before committing to a call that can run for tens of seconds.

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 coverage is 67%; package and display_id are documented, but duration_s has only default and max in the schema with no prose. The description's 'fixed time' gestures at duration_s but gives no default, no 1-50s bound, and no explanation of how package versus display_id is chosen, so the uncovered parameter stays unclear.

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?

States a specific verb and resource (records a display to an MP4) plus the destination (host) and the result (path). It implicitly distinguishes itself from screenshot (still image) by naming the MP4 artifact, though it never names the sibling explicitly.

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 when-to-use guidance at all: nothing says when to prefer this over screenshot, trace, or logcat, and no prerequisites or caveats are given. The only usage-relevant fact, that the recording runs for a fixed time, is stated as behavior rather than as a selection criterion.

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