Skip to main content
Glama
Sign In
Pure Data MCP Server

Pure Data MCP Server

by nikmaniatis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

save_patch

Saves the current Pure Data patch to a user-specified file path.

Instructions

Save the current Pd patch.

This tool saves the current state of the Pure Data patch
to a file at the specified path.

Args:
    file_path: Path to save the patch file
    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": "save_patch"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description must carry burden. Only states it saves to a file. Does not disclose overwrite behavior, required permissions, or error handling. Minimal behavioral insight.

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?

Description is concise and well-structured with a simple sentence followed by Args/Returns. Could be shorter, but no unnecessary content.

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

Completeness3/5

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

For a simple save tool with one parameter and no output schema, it covers the basics. Missing behavioral details like overwrite or errors, but adequate for a minimal tool.

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?

Schema coverage is 0%, but description adds meaning with 'Path to save the patch file'. However, it lacks details on format, relative/absolute paths, or constraints.

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?

Description clearly states 'Save the current Pd patch' with a specific verb and resource. It distinguishes from sibling tools like load_patch by focusing on saving to a file.

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?

Implies usage for saving patches but lacks explicit when-to-use or when-not-to-use guidance. No alternatives mentioned, but context is clear.

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