Skip to main content
Glama

Connect Daydream Cloud

connect_daydream_cloud

Create a Daydream cloud StreamDiffusion bridge: POST source TOP frames to Daydream API, pull diffused results into a null TOP via Syphon/Spout/NDI.

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

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

With no annotations, description carries full burden. It discloses env-var API key, live probe skip, and mechanism (POST to REST, receive via Syphon/Spout/NDI). Does not cover error handling, rate limits, or offline behavior.

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?

Three sentences, front-loaded with main action, no redundant phrases. Each sentence adds value: purpose, auth method, and behavioral note.

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

Completeness4/5

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

For a creation tool with 13 params, description covers core purpose, auth, mechanism, and a caveat. Could mention what happens if key missing, but adequate for typical usage.

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 covers all 13 parameters with descriptions ('server_url' explained as override for self-hosted, 'output_mode' with enum). Description adds minor context (env var for key, probe skip) but mostly overlaps with schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool creates a Daydream cloud-hosted StreamDiffusion bridge. Distinguishes from similar tools like 'drive_streamdiffusion' by specifying cloud-hosted, but no explicit differentiation from other siblings.

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?

Provides some context: API key from env variable, live probe skipped (requires account and HTTPS). However, lacks explicit when-to-use vs. alternatives like 'drive_streamdiffusion' or 'connect_comfyui'.

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