Skip to main content
Glama
Sign In
Manos MCP

Manos MCP

by ryanperkins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Start recording

start_recording

Begin recording UI actions into a session for later export as a replayable Maestro flow or annotated HTML report. Set report mode to capture screenshots after each action.

Instructions

Begin recording subsequent act tools as a session that can be exported to a replayable Maestro flow (export_flow) or an annotated HTML report (export_report). Set report=true to also screenshot after each action for the report.

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

Input Schema

NameRequiredDescriptionDefault
app_idNo
reportNoCapture a screenshot after each action, for export_report

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It states that recording starts, subsequent act tools are captured, and that report=true captures screenshots after each action. This gives the agent actionable behavior insights, though it does not mention side effects like resetting an existing recording or limitations on concurrent sessions.

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?

Two sentences, with the main purpose in the first and the option detail in the second. No fluff, information is front-loaded and easy to skim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and simple parameters, the description adequately covers the tool's core behavior: starting a recording session and selecting screenshot mode. It could mention the relationship with stop_recording or what 'session' means, but the essentials are present and the tool is not highly complex.

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 description coverage is 50% (only 'report' has a schema description). The description adds value for 'report' by explaining it enables screenshots for the report, but 'app_id' is left undocumented in both schema and description, leaving the agent without guidance on what value to supply.

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 clearly states the tool begins recording subsequent act tools as a session, and explicitly names the two export destinations (export_flow, export_report). This distinguishes it from siblings like stop_recording, export_flow, and export_report, and uses a specific verb-resource structure.

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?

The description implies when to use the tool: at the start of a session to capture act tools for later export. It also mentions the optional report flag for screenshot capture, which informs usage. It does not explicitly list exclusions or alternatives, but the context makes the primary use case clear.

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