PureData-MCP

Start Pure Data Live Session

pd_start_live_session

Create and launch a visible, live-edit Pure Data patch with an empty agent-managed canvas, ready for immediate graph replacement.

Instructions

Create and launch a visible live-edit Pd patch with an empty agent-managed canvas ready for pd_live_replace_graph.

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

Input Schema

Name	Required	Description	Default
`dsp`	No
`gui`	No
`overwrite`	No
`targetPath`	No
`audioOutDevice`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Aug 8, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description must disclose side effects but only states the resulting state (visible, empty, agent-managed). It does not mention overwrite behavior, impact on existing sessions, audio output configuration, or whether it stops other sessions, leaving significant behavioral uncertainty.

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 sentence that front-loads the verb and concisely conveys key details. It is efficiently structured without unnecessary words, though it uses domain jargon that could be clearer.

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?

The tool has 5 optional parameters, no annotations, and no output schema, so the description alone must provide complete context. It covers the high-level purpose but leaves parameter semantics and differentiation from siblings unaddressed, making it incomplete for reliable invocation.

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

Parameters1/5

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

The input schema has 5 parameters with 0% description coverage, and the description provides no explanation of dsp, gui, overwrite, targetPath, or audioOutDevice. The agent cannot infer parameter meanings or defaults beyond raw types and defaults.

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 states the action ('Create and launch') and the resource ('visible live-edit Pd patch'), with specific scope ('empty agent-managed canvas ready for pd_live_replace_graph'). It is distinct from generic create tools, but does not explicitly differentiate from sibling pd_create_live_patch.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this is the first step in a live-edit workflow, especially 'ready for pd_live_replace_graph', but it provides no explicit when-to-use guidance or alternatives. It does not mention when to prefer pd_create_live_patch or other siblings.

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