PampaPilot MCP Server

Overview Schema Source Related Servers Discussions Admin

Crear pista en REAPER

create_track

Creates a new track in a REAPER project, validates the track name, and returns a GUID and a reversible transaction for undo.

Instructions

Crea una pista, verifica el nombre y devuelve GUID y transacción reversible.

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": {
      "project_ref": "<project_ref>",
      "name": "<name>"
    },
    "name": "create_track"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`index`	No
`project_ref`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond annotations: it verifies the name, returns a GUID, and mentions the transaction is reversible. It also implies a write operation (create), consistent with readOnlyHint=false. It does not contradict annotations and provides useful side-effect information, though it does not detail all potential impacts (e.g., track index adjustment).

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, concise sentence that is front-loaded with the core action ('Crea una pista') and packs additional useful details (verification, output, reversibility) without waste. Every phrase earns its place.

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?

The description is adequate for a create tool: it states the action, mentions output (GUID and transaction), and implies reversibility. However, it lacks parameter semantics for project_ref and index, and does not address potential side effects or prerequisites. With an output schema present, return details are not fully needed, but the tool's behavior is only partially described, making it minimally viable.

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

Parameters2/5

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

With schema description coverage at 0%, the description should compensate for parameter meaning. It mentions name verification, which gives some context to the 'name' parameter, but it does not explain 'project_ref' or 'index'. The description provides minimal additional value for parameter understanding beyond what the schema already displays.

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 creates a track in REAPER, verifies the name, and returns a GUID and reversible transaction. This specific verb+resource clearly distinguishes it from sibling tools that modify or inspect tracks rather than creating them.

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?

The description provides no guidance on when to use this tool versus alternatives such as import_audio or prepare_song. It does not mention contexts, prerequisites, or exclusions. The only implied usage is that it creates a track, but there is no explicit comparison to sibling tools.

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