Skip to main content
Glama
Sign In
Pure Data MCP Server

Pure Data MCP Server

by nikmaniatis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

load_patch

Replace the current Pure Data patch state by loading a new patch from a specified file path.

Instructions

Load a Pd patch from a file.

This tool loads a Pure Data patch from the specified file path.
It will replace the current patch state.

Args:
    file_path: Path to the patch file to load
    ctx: MCP context
    
Returns:
    Response with status

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": {
      "file_path": "<file_path>"
    },
    "name": "load_patch"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

Discloses that it replaces current patch state, but omits details on error handling, file format restrictions, and effects on DSP. With no annotations, the description carries full burden but is insufficient.

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

Conciseness2/5

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

Contains redundant sentences (first two lines say essentially the same thing). Args list is useful but overall could be more concise and better structured.

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?

Given simplicity of tool, description covers basic function and parameter but does not explain return value details, prerequisites, or relationship to siblings like save_patch. Incomplete for an agent needing precise invocation context.

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

Parameters3/5

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

Description explains file_path parameter meaning, but also mentions ctx which is not a schema parameter. Schema has no descriptions, so this adds some value but is not fully complete.

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?

Clearly states the tool loads a Pd patch file and replaces the current patch state, distinguishing it from save_patch. However, redundant phrasing slightly reduces clarity.

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 on when to use this tool versus alternatives like create_object or clear_workspace. Lacks context for selection.

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

Deploy Server

Other Tools