Skip to main content
Glama
screen-record-mcp

screen-record-mcp

by strubedo

Stop Recording

stop_recording

Stops the current screen recording and finalizes the output file so it is properly saved and playable. Returns stopped=False if no recording is in progress.

Instructions

Stop the current recording so the output file is properly finalized and playable. No-op (returns stopped=False) if no recording is in progress.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses idempotent behavior (no-op) and even the return payload shape ('returns stopped=False'). It does not state permission requirements or what happens on failure mid-finalization, which are the remaining gaps for a mutation of this kind.

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 short sentences, front-loaded with the action and its benefit, followed by the edge case. Nothing is redundant and no sentence could be removed without losing information.

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

Completeness5/5

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

For a zero-parameter, zero-annotation, no-output-schema tool, the description covers the action, the effect on the artifact, and the no-op case, which is everything an agent needs to invoke it correctly. It also compensates for the absent output schema by naming the returned field.

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

Parameters4/5

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

The schema is empty, so the baseline applies and there is no parameter ambiguity to resolve. The description's only semantic addition is the return indicator stopped=False, which is useful context even though it technically describes output rather than input.

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 names a specific verb and resource ('Stop the current recording') and adds the concrete outcome ('output file is properly finalized and playable'), so the agent knows exactly what the call accomplishes and why it matters. Combined with the sibling names start_recording and check_recording_status, there is no ambiguity about which operation this is.

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?

It establishes the triggering condition (a recording is in progress) and explicitly documents the fallback case when there is nothing to stop, which tells the agent it is safe to call unconditionally. It does not explicitly name an alternative tool or ordering (e.g., call before check_recording_status), so it stops just short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.