Skip to main content
Glama
Corvus400

video-capture-mcp

by Corvus400
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

list_active_sessions

List all active screen recording sessions managed by this server process, returning session details like ID, target, and duration.

Instructions

List recording sessions owned by this running server process.

This does not discover recordings started by a dead prior server process;
use cleanup_stale_processes for that case. The response contains a
"sessions" list with session_id, target, target_key, video_path, mode,
started_at, duration_seconds, and pid for each active recording.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Discloses scope limitation (only current process) and lists all response fields; no annotations provided, so description carries burden adequately.

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-sentence description with immediate clarity, no fluff, and logical flow from purpose to constraints to output details.

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 simple list tool with output schema, description covers scope, sibling distinction, and return fields fully.

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?

No parameters exist; schema coverage 100% and baseline for 0 params is 4; description adds no param info as none needed.

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?

Description uses specific verb 'list' and resource 'recording sessions owned by this running server process', clearly distinguishing it from sibling tools like cleanup_stale_processes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when not to use it and provides an alternative tool: 'use cleanup_stale_processes for that case'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Corvus400/video-capture-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server