Skip to main content
Glama

td_stream_top

Stream a TOP continuously with configurable frame rate and JPEG quality. Suppress identical frames to avoid redundancy. Enable base64 image inclusion only when explicitly needed to control token usage.

Instructions

Start continuous TOP stream.

Default mode omits base64 frames to keep token usage low.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fpsNoTarget stream frame rate.
pathYesTOP path to stream continuously.
qualityNoJPEG quality for stream frames.
include_imageNoWhen false (default), streamed resource updates omit base64 image data to reduce token usage. Set true only when you explicitly want frame payloads in context.
emit_unchangedNoWhen false, identical consecutive frames are suppressed.
confirm_high_token_modeNoMust be true when include_image=true. This is an explicit acknowledgement that continuous image payloads can consume many tokens.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already indicate mutable and open-world behavior. Description adds token-saving default mode but omits other traits like confirmation required for images.

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 efficient sentences, front-loaded with purpose. No wasted words.

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?

With output schema and 6 parameters, description is too minimal. Lacks lifecycle, error, or stream management details.

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 has 100% parameter description coverage. Description adds minimal value, only relating to include_image default behavior.

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 clearly states 'Start continuous TOP stream' with a specific verb and resource. It distinguishes from sibling 'td_stop_stream_top'.

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

Usage Guidelines2/5

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

No explicit guidance on when to use versus alternatives. Only mentions default mode, not when-not to use or prerequisites.

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/dreamrec/TDPilot'

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