tdmcp

Create NCAM camera tracking bus

create_ncam_camera_tracking_bus

Creates an NCAM camera tracking scaffold for TouchDesigner, including pose, lens, video preview, and calibration maps.

Instructions

Create an NCAM camera-tracking scaffold with pose, lens, video-preview, and calibration maps.

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_ncam_camera_tracking_bus"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Generated baseCOMP name.	ncam_camera_tracking_bus
`port`	No
`active`	No
`parent_path`	No	Parent COMP for the NCAM scaffold.	/project1
`camera_count`	No
`include_video_top`	No
`lens_profile_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already indicate a write/create operation (readOnlyHint=false, openWorldHint=true), and the description aligns with that. However, it adds no behavioral context beyond the annotation, such as what the scaffold modifies, side effects, or how it interacts with the existing network.

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 a single, efficient sentence that immediately communicates the tool's purpose. No wasted words, and it is appropriately front-loaded with the action verb 'Create'.

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?

For a 7-parameter tool with a large sibling set, the description is too sparse. It omits usage guidelines, parameter semantics, and deeper behavioral details, relying solely on annotations that provide limited context.

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 29% (2 of 7 parameters have descriptions), and the tool description does not compensate by explaining any parameters. The listed maps ('pose, lens, video-preview, calibration') are internal components, not parameter explanations.

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 'NCAM camera-tracking scaffold' with specific map types, using a specific verb and resource. It distinguishes from sibling tracking buses by explicitly naming NCAM, which is a unique tracking system.

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 versus the many sibling tracking bus creators (e.g., OptiTrack, Blacktrax). The description lacks any context about prerequisites, alternatives, or exclusionary conditions.

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

Deploy Server