bad-ass-mcp

Overview Schema Source Related Servers Discussions Admin

stop_recording

Stops an active screen recording and exports the capture to a .gif or .mp4 file, returning the saved file path for use in docs or READMEs.

Instructions

Stop recording and export.

output_path must end in .gif or .mp4. GIF is transcoded and downscaled to 900px wide at 12 fps, fine for a short clip in a README. MP4 keeps the full-resolution H.264 capture with no re-encode, so use it for anything longer than a minute or two (a 20-minute GIF is both huge and slow to build). Returns the path to the finished file.

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": {
      "handle": "<handle>",
      "output_path": "<output_path>"
    },
    "name": "stop_recording"
  }
}

Input Schema

Name	Required	Description	Default
`handle`	Yes
`output_path`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A4.2/5.0

Behavior4/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 and does well: it discloses that GIF output is transcoded and downscaled to 900px/12fps while MP4 is a full-resolution H.264 capture with no re-encode, plus the performance implication of long GIFs. The notable gap is that it never says what happens to the recording handle after stopping or whether it can be reused.

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?

Front-loaded with the action, followed by the hard constraint on output_path, then the format tradeoff with its justification. Every sentence carries information; the parenthetical about a 20-minute GIF earns its space by making the size tradeoff concrete.

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?

With no output schema, the description usefully states that the finished file path is returned. For a two-parameter finalization tool it is nearly complete, but the unexplained handle parameter is the one thing an agent could still get wrong.

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 0%, so the description must compensate for both parameters. It explains output_path thoroughly (required .gif or .mp4 suffix, resolution/fps/encoding consequences per format), but the handle parameter's meaning and provenance are never addressed, leaving half the contract undocumented.

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?

"Stop recording and export" gives a specific verb and resource, and the implied pairing with start_recording makes the role obvious. An agent knows immediately this finalizes a live capture rather than starting one.

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 gives concrete decision guidance for the format choice: GIF for a short README clip, MP4 for anything longer than a minute or two, with the reason (a 20-minute GIF is huge and slow to build). It doesn't state explicit prerequisites, such as that a recording must be active or where handle comes from, which keeps it short of a 5.

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

Deploy Server