Skip to main content
Glama
nikmaniatis

Pure Data MCP Server

by nikmaniatis

connect_objects

Create a connection between two Pure Data objects by specifying the source outlet and destination inlet ports to link them with a patch cord.

Instructions

Create a connection between two Pd objects.

This tool connects two objects in the Pure Data patch by creating a
patch cord between the specified outlet and inlet.

The connection system uses numeric indices rather than string IDs,
as required by the Pure Data patch. The global object_indices
dictionary maps from the user-friendly string IDs to these numeric indices.

Args:
    source: Source object with id and port
           e.g., {"id": "osc~_100_100", "port": 0}
    destination: Destination object with id and port
                e.g., {"id": "dac~_200_100", "port": 0}
    ctx: MCP context
    
Returns:
    Response with status
    
Example:
    connect_objects({"id": "osc~_100_100", "port": 0}, {"id": "dac~_200_100", "port": 0}, ctx)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYes
destinationYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the numeric index mapping and basic action, but does not disclose side effects (e.g., duplicate connections, limits, or permission requirements).

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 somewhat verbose with docstring-style sections (Args, Returns, Example). While structured, it could be more concise by removing redundant phrasing like 'e.g.,' and 'This tool...'.

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 the complexity (nested objects, no output schema, no annotations), the description provides examples, explains the numeric index system, and clarifies parameter structure. It adequately covers the essential context.

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 provides minimal info (objects with no properties). Description adds meaning by specifying that source and destination have 'id' and 'port' fields, and provides concrete examples. With 0% schema coverage, this compensates well.

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 states exactly what the tool does: 'Create a connection between two Pd objects' by creating a patch cord. It clearly distinguishes from the sibling 'disconnect_objects' which does the opposite.

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 does not explicitly state when to use this tool vs alternatives. It implies usage for connecting objects but lacks 'when not to use' or explicit context compared to siblings like create_object or disconnect_objects.

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