Skip to main content
Glama
anilyesilkaya

Marey

by anilyesilkaya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

record

Capture screen activity for a set duration and generate a timestamped contact sheet image to inspect motion like animations and UI transitions.

Instructions

Record the screen for a fixed duration and return a numbered, timestamped contact sheet (a grid of still frames) as an image. Use this to inspect motion: dragging, animations, flashes, reordering, anything that cannot be understood from a single screenshot. Raw frames are also saved to disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fpsNoFrames captured per second (default 2).
colsNoThumbnails per contact-sheet row. Overrides the detail preset. Fewer columns = larger, more legible cells.
delayNoSeconds to wait before recording starts (default 0).
titleNoWindow-title substring to match when region is "window".
detailNoLegibility preset for the contact sheet (default "overview"). A returned image has a fixed resolution budget split across columns, so fewer/wider cells show more. "overview" = 4 cols @ 480px (many frames at a glance); "high" = 2 cols @ 760px (UI text usually readable); "max" = 1 col @ 1280px (closest to raw frames). Use "high"/"max" when fine detail or small text matters. Explicit cols/thumbWidth override this.
regionNoprimary monitor, the full virtual desktop, or a window (default primary). Prefer "window" when a single app is involved: a smaller source means each thumbnail keeps more detail.
secondsNoRecording duration in seconds (default 5).
thumbWidthNoThumbnail width in pixels. Overrides the detail preset. Note: has little effect once the sheet exceeds the client's inline-image size cap — reduce cols instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / cols / description
      Previous value: -"Thumbnails per contact-sheet row (default 4)."New value: +"Thumbnails per contact-sheet row. Overrides the detail preset. Fewer columns = larger, more legible cells."
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "Legibility preset for the contact sheet (default \"overview\"). A returned image has a fixed resolution budget split across columns, so fewer/wider cells show more. \"overview\" = 4 cols @ 480px (many frames at a glance); \"high\" = 2 cols @ 760px (UI text usually readable); \"max\" = 1 col @ 1280px (closest to raw frames). Use \"high\"/\"max\" when fine detail or small text matters. Explicit cols/thumbWidth override this.",
+  "enum": [
+    "overview",
+    "high",
+    "max"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / region / description
      Previous value: -"primary monitor, the full virtual desktop, or a window (default primary)."New value: +"primary monitor, the full virtual desktop, or a window (default primary). Prefer \"window\" when a single app is involved: a smaller source means each thumbnail keeps more detail."
    • changedInput schema / properties / thumbWidth / description
      Previous value: -"Thumbnail width in pixels (default 480)."New value: +"Thumbnail width in pixels. Overrides the detail preset. Note: has little effect once the sheet exceeds the client's inline-image size cap — reduce cols instead."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does disclose a real side effect — raw frames are saved to disk — and that recording blocks for a fixed duration, but it omits permissions, whether files persist/is cleaned up, and how it interacts with the start_recording/stop_recording siblings.

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?

Three tight sentences, front-loaded with what the tool does, then the use case, then the disk side effect. No filler or redundancy.

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?

Explains the return artifact and its purpose, and the schema fully documents all 8 optional parameters, so an agent can call it correctly. It could say a bit more about the disk artifacts and interaction with the recording siblings, but nothing essential is missing.

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 100% and all eight parameters carry their own detailed descriptions (defaults, enum meanings, override behavior), so the description adds no parameter detail. Baseline 3 is appropriate when the schema does all the work.

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 (Record) and resource (screen) plus the exact output artifact — a numbered, timestamped contact-sheet image. It implicitly distinguishes itself from the single-shot sibling by scoping itself to 'anything that cannot be understood from a single screenshot,' though it never names an alternative directly.

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 when-to-use trigger ('inspect motion: dragging, animations, flashes, reordering') and the contrast condition against single screenshots. It stops short of naming siblings like get_frame or start_recording or stating when NOT to use this tool.

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