Skip to main content
Glama
beekamai
by beekamai

stream_list

List active and completed stream sessions from the screenshot process to monitor and manage ongoing captures.

Instructions

List active and completed stream sessions known to this process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The listStreams() function is the handler/implementation for the stream_list tool. It iterates over all stream sessions and returns basic info (id, done, frameCount, remainingMs) for each.
    export function listStreams(): Array<{ id: string; done: boolean; frameCount: number; remainingMs: number }> {
      const out: Array<{ id: string; done: boolean; frameCount: number; remainingMs: number }> = [];
      for (const s of sessions.values()) {
        out.push({
          id: s.id,
          done: s.done,
          frameCount: s.frames.length,
          remainingMs: Math.max(0, s.stopAt - Date.now()),
        });
      }
      return out;
    }
  • src/index.ts:150-154 (registration)
    Tool registration: stream_list is registered via ListToolsRequestSchema with name 'stream_list', description, and empty inputSchema (no params).
    {
      name: "stream_list",
      description: "List active and completed stream sessions known to this process.",
      inputSchema: { type: "object", properties: {} },
    },
  • src/index.ts:236-237 (registration)
    The stream_list case in CallToolRequestSchema switch dispatches to listStreams() imported from ./stream.js.
    case "stream_list":
      return text(listStreams());
  • Import of the listStreams function from ./stream.js at the top of index.ts.
    import {
      startStream,
      stopStream,
      snapshotStream,
      listStreams,
      dropStream,
    } from "./stream.js";
Behavior2/5

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

No annotations provided; description only states it lists sessions without disclosing side effects, performance, or what 'known to this process' entails.

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?

Single sentence, 8 words, no fluff; every word is necessary and efficient.

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

Completeness3/5

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

Given no output schema and sibling tools, description lacks details on return format or scope; leaves ambiguity about 'known to this process'.

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, so schema coverage is 100%; description needs no additional parameter info, but baseline for zero params is 4.

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 'stream sessions', clearly distinguishing from sibling tools like stream_drop, stream_start, etc.

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

Usage Guidelines3/5

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

Implied usage for listing sessions, but no explicit when-to-use or alternatives compared to siblings like stream_latest or stream_status.

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/beekamai/mcp-screenshot'

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