tdmcp

Connect A1111 WebUI bridge

connect_a1111_webui_bridge

Create a Stable Diffusion WebUI scaffold with prompt slots, result maps, ControlNet hints, and adapter notes for connecting TouchDesigner to AUTOMATIC1111.

Instructions

Create an AUTOMATIC1111/Forge Stable Diffusion WebUI handoff scaffold with prompt slots, result maps, ControlNet hints, and adapter notes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "connect_a1111_webui_bridge"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Generated baseCOMP name.	a1111_webui_bridge
`active`	No
`server_url`	No	WebUI or adapter base URL.	http://127.0.0.1:7860
`parent_path`	No	Parent COMP for the WebUI scaffold.	/project1
`endpoint_kind`	No		txt2img
`output_folder`	No		./generated/a1111
`prompt_slot_count`	No
`include_controlnet`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The description adds useful context by calling it a 'scaffold' rather than an actual live connection, implying it builds a structure instead of connecting to a server. However, annotations already convey create/non-read-only/non-destructive intent, and the description does not reveal side effects, file output, or network behavior beyond that.

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?

A single sentence that is front-loaded with the verb 'Create' and packs all key features without fluff. It is efficient and well-structured, earning its place.

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

Completeness2/5

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

With 8 parameters and no output schema, the description needs to set expectations for the scaffold's structure and how parameters affect it. It only lists high-level feature names and omits return values, parameter-specific behavior, or post-creation expectations, making it incomplete for moderate complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 38%, and the description partially maps to just two parameters (prompt_slot_count via 'prompt slots', include_controlnet via 'ControlNet hints'). It does not explain server_url, endpoint_kind, output_folder, active, or parent_path semantics, leaving significant gaps for the agent.

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 an AUTOMATIC1111/Forge Stable Diffusion WebUI handoff scaffold with specific components (prompt slots, result maps, ControlNet hints, adapter notes), distinguishing it from sibling bridge tools like connect_comfyui for other image-generation backends.

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 guidance is provided on when to use this tool vs alternatives. The description only states what the tool creates; it does not compare to other bridge tools or specify prerequisites, exclusions, or preferred scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server