tdmcp

Connect OSCQuery namespace

connect_oscquery_namespace

Set up an OSCQuery HTTP namespace with OSC send/receive channels and action maps for building live-control apps.

Instructions

Create an OSCQuery HTTP namespace and OSC send/receive scaffold with action maps for live-control apps.

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

Input Schema

Name	Required	Description	Default
`name`	No	Generated baseCOMP name.	oscquery_namespace
`active`	No
`http_port`	No
`parent_path`	No	Parent COMP for the OSCQuery scaffold.	/project1
`action_count`	No
`service_host`	No	OSCQuery HTTP service host.	127.0.0.1
`osc_send_port`	No
`namespace_root`	No	OSCQuery namespace root path.	/
`osc_receive_port`	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 that it creates namespace, scaffold, and action maps, which gives some context beyond the annotations (readOnly=false, destructive=false). However, it does not disclose side effects like whether it starts HTTP services, generates COMPs, or modifies existing nodes. It is not contradictory, but it is only minimally transparent given the openWorldHint.

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, front-loaded sentence that conveys the core purpose without wasted words. It is appropriately sized for the tool type, though it sacrifices detail for brevity.

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 tool with 9 parameters, no output schema, and minimal annotations, this description is incomplete. It does not explain what the scaffold includes, how the OSCQuery namespace is used, or what 'action maps' mean. It lacks the needed context for an agent to select and invoke it correctly among many connection tools.

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?

With only 44% schema description coverage, the description's single sentence provides no additional parameter explanations. Parameter names are self-explanatory to limited extent, but the description does not clarify relationships (e.g., how action_count relates to action maps, or how ports are wired). It fails to compensate for the schema's gaps.

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 a specific action ('Create an OSCQuery HTTP namespace and OSC send/receive scaffold with action maps') with a defined resource and purpose ('for live-control apps'). It distinguishes itself from sibling tools like connect_ableton_link_session or create_midi_map by naming the OSCQuery HTTP namespace and OSC scaffold.

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 explicit guidance on when to use this tool versus alternatives. It only implies it is for live-control apps, but does not mention prerequisites, exclusions, or preferred sibling tools. There is no 'when not to use' or alternative recommendation.

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

Deploy Server