Skip to main content
Glama

td_screenshot

Read-onlyIdempotent

Capture a TOP frame as base64 inline or save to disk for visual verification. Without a save path, returns base64 data; set save_path for token-efficient metadata-only response.

Instructions

Capture a TOP frame as base64 inline, or to disk via save_path.

Use this for a quick single-frame visual: with save_path set the image is written to disk TD-side and only metadata + the path come back — use this for repeated visual verification. Without it the response embeds base64 image data; ask the user before repeated base64 screenshots because each image can consume significant tokens in model context. Prefer td_capture_frame when you want metadata-first (resolution/format/bytes) with the image behind a confirm/save_path gate; prefer td_capture_and_analyze when you also need cooking state and errors folded into the same call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to a TOP node to capture as an image (e.g. '/project1/null1', '/project1/render1')
qualityNoJPEG quality from 0.0 (smallest) to 1.0 (best). Default 0.5 gives good diagnostic quality at ~85KB.
save_pathNoOptional disk destination. When set, TouchDesigner writes the image to this path and the tool returns metadata + the saved path with NO base64 payload (near-zero token cost — the cheap visual-verify loop). Accepts an absolute path under your home directory or a bare filename (saved under ~/.tdpilot/captures/). Extension must be .png/.jpg/.jpeg.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds important context about base64 images consuming significant tokens, which is beyond annotation scope.

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?

The description is concise, well-structured, and front-loaded with the main action. Every sentence adds value with no redundancy.

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?

Given 3 parameters, 100% schema coverage, presence of output schema, and rich annotations, the description provides complete guidance on both modes and their appropriate use cases.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the trade-off between base64 and disk saves, and how quality affects size, augmenting the schema.

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?

The description clearly states the tool captures a TOP frame either as base64 inline or to disk via save_path, and distinguishes from sibling tools td_capture_frame and td_capture_and_analyze.

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 advises when to use save_path (repeated visual verification, low token cost) vs without (single frame, but warn user about token consumption). Also recommends sibling tools for alternative workflows.

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