Skip to main content
Glama
Sign In
Flutter Driver MCP

Flutter Driver MCP

by funkyfunc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

stop_recording

Stop an active screen recording and finalize the video file. Get file path, format, duration, and size in one call.

Instructions

Stops the current screen recording and finalizes the video file. Returns the file path, format, duration, and file size. Called automatically by stop_app if a recording is active.

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.2.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries the burden. It discloses the behavioral result (finalizes video file) and return values (path, format, duration, size). However, it doesn't describe error behavior when no recording is active, or any side effects, which would benefit from disclosure given zero annotation coverage.

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 tightly-scoped sentences. First states the action and result, second lists return values, third clarifies the automatic-call relationship with stop_app. Zero wasted words.

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?

For a parameterless tool with no output schema, the description covers the action, return values, and relationship to stop_app. Minor gap: doesn't address what happens if no recording is active (error vs no-op), which an agent might need to know. But given the tool's simplicity, it's largely complete.

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?

Tool has 0 parameters, so schema carries no burden. The description compensates by explaining return values clearly (file path, format, duration, file size), which is the meaningful semantic content for this parameterless tool. Baseline 4 for 0 params is appropriate.

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?

Clear verb+resource (stops recording) with explicit outcomes (finalizes video file, returns file path, format, duration, file size). Well-defined scope that distinguishes it from sibling start_recording.

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?

Mentions it's called automatically by stop_app if a recording is active, which gives useful context about when it's invoked. Doesn't explicitly state when NOT to use it or name alternatives, but the automatic-call note and sibling context make usage fairly clear.

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