tdmcp

Create TouchOSC layout

create_touchosc_layout

Generate a TouchOSC-style OSC mapping surface and JSON manifest DAT for TouchDesigner, with configurable controls and network settings.

Instructions

Create a TouchOSC-oriented OSC mapping surface and JSON manifest DAT. This intentionally does not claim to generate TouchOSC .tosc documents.

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": "create_touchosc_layout"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Generated baseCOMP name.	touchosc_layout
`controls`	No	TouchOSC-style controls to expose as OSC mapping rows.
`page_name`	No		tdmcp
`send_host`	No		127.0.0.1
`send_port`	No
`parent_path`	No	Parent COMP for the TouchOSC surface.	/project1
`receive_port`	No
`create_manifest_dat`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

B3/5.0

Behavior3/5

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

The annotations already indicate this is a non-read-only, non-destructive, open-world creation tool, so the description doesn't need to restate that. It adds the valuable behavioral note that it does not generate .tosc documents, which is useful context. However, it lacks detail on side effects like network binding, project structure changes, or the exact nature of the JSON manifest, so transparency is partial.

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 exceptionally concise, using exactly two sentences: one to state the primary purpose and one to set an important boundary. No redundant or filler content exists, making it easily scannable. The structure is front-loaded with the verb and resource, aligning well with clarity goals.

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?

This tool has 8 parameters, no output schema, and low parameter description coverage, yet the description remains a minimal statement. It doesn't explain how the controls array maps to OSC, what the JSON manifest DAT contains, or how the surface integrates into a TouchDesigner project. The .tosc disclaimer is helpful but insufficient for a tool of this 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%, so the description carries a responsibility to clarify the undocumented parameters. Mentioning 'OSC' hints at network-related params (send_host, send_port, receive_port) but doesn't explain their specifics, defaults, or the meaning of page_name and create_manifest_dat. The description adds little value beyond the sparse schema entries.

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?

The description clearly identifies the tool as creating a 'TouchOSC-oriented OSC mapping surface and JSON manifest DAT', using a specific verb and resource. It also distinguishes itself by explicitly stating it does not generate .tosc documents, which clarifies its scope. However, it doesn't reference sibling tools (e.g., create_control_surface, create_midi_map) for direct comparison, preventing a perfect score.

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?

The description provides minimal guidance on when to use this tool. The note about not generating .tosc documents implies a boundary but doesn't offer positive use cases or compare alternatives like create_control_surface or create_phone_remote. No prerequisites or workflow context are given, leaving the agent without clear direction.

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

Deploy Server