Skip to main content
Glama

record

Capture a macOS app window to MP4 for demos, showing an animated cursor at each action in real time. Start capturing, perform steps, then stop to save the video.

Instructions

Record a window to MP4 for a demo: start, act, then call with stop. The video shows an animated cursor at each action, in real time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app": "<app>"
    },
    "name": "record"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes
outNoMP4 path
stopNo
labelNoCursor name
windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses that output is MP4, that recording is real time, and that an animated cursor is rendered at each action, but it omits permissions needed, what happens if recording is already running, and whether the file path is returned.

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?

Two short sentences, front-loaded with the core action and followed by the call sequence. Slightly terse phrasing ('call with stop') costs a little clarity but nothing is wasted.

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 five-parameter tool with no annotations and no output schema, the description should say what is returned and what the required 'app' scope means. The omission of the required parameter's meaning and the return value leaves material gaps.

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 40%, and the description compensates for the undocumented channel only partially: it implies 'window' selects the capture target and that 'stop' ends recording. The required 'app' parameter and the distinction between 'app' and 'window' have no explanation anywhere, and 'label' remains ambiguous ('Cursor name').

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 ('Record a window to MP4') with the intended purpose (a demo), which clearly separates it from read-only siblings like observe or see. It stops short of explicitly contrasting itself with any named sibling, keeping it out of the top band.

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?

Gives a concrete workflow: 'start, act, then call with stop,' which tells the agent both the sequencing and the sibling it orchestrates. No explicit when-not guidance (e.g., don't record if a session is already active) is offered.

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