Record up to 30 seconds of Android device screen as MP4, then download and delete the file from temporary storage. Use for capturing animations, transitions, or gameplay clips.
Rovid (max 30 mp) kepernyofelvetel keszitese MP4 formatumban.
Hasznos animaciok, atmenetek, jatekmenet visszanezesehez. A felvetel az eszkoz ideiglenes tarhelyere kerul, majd letoltodik es torlodik onnan.
| Name | Required | Description | Default |
|---|---|---|---|
| serial | No | ||
| seconds | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the behavioral disclosure burden. It does so by stating the 30-second cap, MP4 format, temporary device storage, and subsequent download-and-delete lifecycle. It omits permissions and error behavior, but the main side effects are covered.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact: two sentences, with the core purpose front-loaded and the use cases and lifecycle details after. There is no redundant wording, though a slightly more structured format could improve scannability.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is minimally complete for a simple tool: it conveys what is recorded, the format, duration limit, and storage lifecycle. However, it leaves parameter semantics and the tool's return/output behavior undefined, which matters because there is no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain the 'serial' or 'seconds' parameters. The 'max 30 mp' hint weakly implies that 'seconds' controls duration, but 'serial' is never clarified, so the description fails to compensate for the absent schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: creating a short screen recording (max 30 seconds) in MP4 format. It distinguishes video capture from static screenshot tools, though it does not explicitly name a sibling alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says the tool is useful for animations, transitions, and gameplay replay, giving an agent context for when video recording is appropriate. It does not, however, mention when not to use it or name an alternative tool directly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.