Skip to main content
Glama
Sign In
Local MCP

Local MCP

by colibird-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

screen_record_start

Start recording your Mac screen by selecting a display, window, or region. Capture exactly what you need for tutorials or troubleshooting.

Instructions

Begins a screen recording (ScreenCaptureKit) of a display, window, or region.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.336

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are present, so the description bears full responsibility for conveying behavioral traits. It does not disclose permissions, side effects, or what happens if a recording is already in progress. The description lacks essential behavioral context.

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

Conciseness3/5

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

The description is a single sentence, concise but overly terse. It could include more detail without being verbose, such as mentioning default behavior or how to specify the target. The structure is acceptable but lacks necessary information.

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

Completeness2/5

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

Given the lack of annotations, output schema, and parameters, the description should provide more context about recording behavior, resolution settings, or constraints. It is insufficient for an agent to understand the tool's full usage and implications.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, but the description mentions recording 'a display, window, or region,' implying the need for target selection, which is not reflected in the schema. This inconsistency undermines clarity. Baseline of 4 for zero parameters is not warranted due to misleading information.

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's function: 'Begins a screen recording (ScreenCaptureKit) of a display, window, or region.' The verb 'begins' is specific, and it identifies the resource (screen recording) and targets (display, window, region). It distinguishes itself from sibling tools like screen_record_status and screen_record_stop.

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 guidance is provided on when to use this tool versus alternatives such as screenshot_capture or video recording tools. There is no mention of prerequisites or context for use.

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