Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

add_track_to_group

Add a track to a specified group while rejecting implicit transfers from another group, ensuring explicit membership changes.

Instructions

Add a route to a group; reject implicit transfer from another group.

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": {
      "request": "<request>"
    },
    "name": "add_track_to_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
successNo
warningsNo
revision_afterNo
changed_objectsNo
revision_beforeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive mutation, so the description's added value is the rejection rule for cross-group transfer -- genuine failure-mode context. It says nothing about dry_run, confirm_delete, or expected_revision conflict behavior, all of which materially change what the call does, so the disclosure is only partial.

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?

A single compact sentence with the action front-loaded and the constraint following, which is good structure. The only cost is the ambiguous "route" wording that forces interpretation.

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?

An output schema exists, so return values need not be described, and the rejection rule covers the main surprise failure. But for a mutation tool with a rich nested request object at 0% schema coverage, the absence of any guidance on dry_run, confirm_delete, and expected_revision leaves the definition thin relative to its complexity.

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?

Schema description coverage is 0% and the request object carries five fields (group_id, track_id, dry_run, confirm_delete, expected_revision), yet the description names none of them and explains none of their effects. The only implicit mapping is "route"->track_id and "group"->group_id; the semantics of dry_run, confirm_delete, and expected_revision are left entirely undocumented.

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?

"Add a route to a group" names a specific verb and target resource, and the trailing clause narrows the scope further. It is slightly undercut by terminology drift -- the tool is about tracks (track_id in the schema) but the description says "route" -- so an agent must bridge that gap, though the operation itself is still identifiable.

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?

"Reject implicit transfer from another group" communicates a when-not condition: this call fails rather than silently moving a track that already belongs elsewhere, which implies the caller should remove it first. However, no sibling tool is named (remove_track_from_group is the obvious counterpart) and no positive prerequisites are stated.

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