tdmcp

Create BlackTrax tracking bus

create_blacktrax_tracking_bus

Set up a BlackTrax tracking scaffold with receiver, trackable maps, zone maps, and calibration notes. Configure port, active status, and counts for trackables and zones.

Instructions

Create a BlackTrax tracking scaffold with receiver, trackable maps, zone maps, and calibration 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": "create_blacktrax_tracking_bus"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Generated baseCOMP name.	blacktrax_tracking_bus
`port`	No
`active`	No
`zone_count`	No
`parent_path`	No	Parent COMP for the BlackTrax scaffold.	/project1
`trackable_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive open-world operation. The description adds that the scaffold includes receiver, trackable maps, zone maps, and calibration notes, offering some scope of what gets created. However, it does not disclose side effects like network connectivity, whether it overwrites existing components, or how the active parameter influences behavior. It adds modest value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the core action and enumerates components without redundancy. It is appropriately sized and easy to parse, though the jargon 'scaffold' and 'trackable maps' might be slightly unclear to an unfamiliar agent.

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 six parameters and no output schema, the description does not provide enough operational detail. It omits parameter behavior, prerequisites (e.g., parent_path must exist), return values, and failure modes. The high-level overview leaves many questions unanswered for a complex scaffold-creation tool, making it insufficient for confident invocation.

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 33%, and the description does not explicitly explain any of the six parameters. While 'zone maps' and 'trackable maps' hint at the roles of zone_count and trackable_count, there is no mapping for port, active, or parent_path beyond the sparse schema descriptions. The description fails to compensate for the low schema coverage.

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 BlackTrax tracking scaffold and names its key components (receiver, trackable maps, zone maps, calibration notes), making the action and scope explicit. It uniquely identifies the resource (BlackTrax) which distinguishes it from sibling tracking-bus tools like create_optitrack_tracking_bus.

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 gives no guidance on when to use this tool versus other tracking-bus or scaffold tools, nor does it mention prerequisites or exclusions. The only implied usage is the verb 'create', which is too vague for deciding between this and similar tools in the large sibling set.

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

Deploy Server