PureData-MCP

Disconnect Live Pure Data Objects

pd_live_disconnect

Disconnect an agent-created live connection by its stable ID, then rebuild the visible MCP live canvas.

Instructions

Remove an agent-created live connection by stable id, then rebuild the visible MCP live canvas.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "pd_live_disconnect"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Aug 8, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose a key side effect: rebuilding the visible MCP live canvas after removal. However, it does not mention irreversibility, what happens if the id does not exist, or whether there are any prerequisites, which leaves some 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.

Conciseness5/5

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

The description is a single, well-structured sentence that immediately states the action and the follow-up side effect. There is no redundant or vague wording, making it optimally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter removal tool, the description is adequately complete. It identifies the target (agent-created connection by stable id) and the consequence (canvas rebuild). It does not detail error behavior, but this is not essential for a simple inverse of pd_live_connect, especially with no output schema.

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

Parameters4/5

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

The schema describes the 'id' parameter with a pattern but no description. The tool description adds the semantic clue that this is a 'stable id' for an agent-created connection, which helps the agent infer that this is the id returned from a previous connect operation. This compensates well for the otherwise bare schema.

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 removes an agent-created live connection using a stable id, and also notes that it rebuilds the visible canvas afterward. This specific verb+resource+method distinguishes it from sibling tools like pd_live_connect and pd_live_remove_object.

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

Usage Guidelines4/5

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

The phrase 'agent-created live connection' provides clear context that this tool is intended for connections previously created by the agent, and 'stable id' indicates the id comes from a prior creation. It does not explicitly name alternatives or when-not-to-use scenarios, but the scope is clearly delimited.

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