Skip to main content
Glama

Connect Daydream Cloud

connect_daydream_cloud

Create a Daydream cloud bridge to send frames from a TOP to the StreamDiffusion API and receive diffused results in TouchDesigner.

Instructions

Create a Daydream cloud-hosted StreamDiffusion bridge in TD. A webclientDAT POSTs the encoded source TOP frame to Daydream's REST endpoint; the diffused result is pulled back via a Syphon/Spout/NDI receiver and exposed as a null TOP. API key is read from DAYDREAM_API_KEY in the TD process environment — never inlined. Live probe SKIPPED (requires Daydream account + outbound HTTPS).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fpsNoOutbound POST cadence; clamped 1–30 (cloud rate-limit guard).
nameNoContainer name; defaults to daydream_cloud1.
seedNoOptional seed.
activeNoStart polling immediately (default off so artist can confirm API key is set).
promptNoText prompt sent in the request body.
model_idNoDaydream model slug.streamdiffusion-v1
strengthNoDiffusion strength.
server_urlNoDaydream inference endpoint. Override for self-hosted or staging.https://api.daydream.live/v1/stream
output_modeNoReceiver TOP to instantiate for the relay output.syphon
parent_pathNoCOMP to create the bridge sub-network in./project1
expose_controlsNoAdd custom-page sliders (Prompt, Strength, FPS, Active).
source_top_pathYesTOP whose frames are POSTed to Daydream.
output_source_nameNoNDI source / Syphon-Spout sender name to subscribe to.daydream_out
Behavior4/5

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

Beyond annotations (readOnlyHint false, openWorldHint true), the description adds behavioral details: API key from environment variable, data flow mechanism, and that live probe is skipped. No contradiction with annotations.

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 (3-4 sentences), front-loaded with purpose, and efficiently covers data flow, security, and a limitation. Every sentence adds value.

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?

While the description explains the process well, it lacks information about return values (no output schema) and error handling. Given the complexity (13 params, external service), this gap reduces completeness.

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?

Input schema has 100% description coverage, so parameters are well-documented. The tool description adds process context but does not significantly enhance meaning beyond schema for individual parameters. Baseline 3 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?

The description clearly states the tool creates a Daydream cloud-hosted StreamDiffusion bridge in TD, specifying the verb 'Create' and the resource. It details the data flow (POST source, receive via receiver) and differentiates from siblings like connect_comfyui by naming Daydream.

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?

The description mentions prerequisites (Daydream account, outbound HTTPS) and that a live probe is skipped, but does not explicitly guide when to use this tool vs alternatives or provide exclusions. Usage context is implied but not fully specified.

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/Pantani/tdmcp'

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