Skip to main content
Glama
nikmaniatis

Pure Data MCP Server

by nikmaniatis

create_object

Create a new Pure Data object at a given position with specified type and arguments, and receive a unique ID for later connections and modifications.

Instructions

Create a new Pd object.

This tool creates a new object in the Pure Data patch at the specified position.
The object can be any valid Pd object type (e.g., osc~, dac~) with optional arguments.

The implementation handles:
1. Creating the object in Pure Data via OSC
2. Assigning a unique numeric index to the object for connection tracking
3. Returning an object_id that can be used in subsequent API calls

The object_id follows the format "{object_type}_{x}_{y}" to provide
a predictable way to reference objects.

Args:
    object_type: Type of Pd object (e.g., osc~, dac~)
    args: Arguments for the object (e.g., ["440"] for an oscillator)
    position: Position on the canvas (x, y coordinates)
    ctx: MCP context
    
Returns:
    Response with object ID and status
    
Example:
    create_object("osc~", ["440"], {"x": 100, "y": 100}, ctx)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYes
positionYes
object_typeYes
Behavior4/5

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

No annotations provided, so description carries full burden. It describes the creation process via OSC, unique index assignment, and object_id format. Lacks mention of permissions or side effects, but covers core behavior well.

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

Conciseness3/5

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

The description is fairly long with repeated information (e.g., 'Create a new Pd object' appears twice). It includes an example call, which is useful, but could be more concise. Structure is logical with sections.

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?

Given complexity (3 params, nested objects, no output schema), the description is fairly complete. Explains return value and object_id format. Covers main aspects adequately.

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?

Schema coverage is 0% (no descriptions in schema). The description adds meaning: object_type as Pd object type (e.g., osc~), args as arguments array (e.g., ['440']), position as x,y coordinates. This compensates for the schema gap.

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 it creates a new Pd object in a Pure Data patch at a specified position, specifying object type and arguments. It distinguishes from siblings like delete_object and connect_objects.

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 explains the tool's purpose but does not explicitly state when to use it vs alternatives. It mentions the returned object_id for subsequent API calls, but no exclusion criteria or when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nikmaniatis/Pd-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server