Skip to main content
Glama
Sign In
mcp-svstudio

mcp-svstudio

by shotarokawade
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_notes

Delete unwanted notes from Synthesizer V Studio projects by specifying note indices or a locator to clean up your composition.

Instructions

Delete note(s) from a group by noteIndices or locator.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
locatorNo
noteIndexNoSingle 0-based note index to delete
groupIndexNo
trackIndexNo
noteIndicesNoArray of 0-based note indices to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of explaining behavior. It only states that deletion happens, and omits important behavioral details: the dry_run preview mode, whether locator matching deletes all matching notes, irreversibility, and whether the operation returns anything.

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?

The description is a single, front-loaded sentence with no filler. The phrasing 'note(s)' is slightly awkward, but the sentence is efficient and communicates the core operation quickly.

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

Completeness2/5

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

Given six parameters, a nested locator object, no output schema, and no annotations, a one-sentence description is too thin. It leaves ambiguous behavior around dry_run, locator matching semantics, and the result of the operation.

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 only 33% and the description compensates only partially. It explains that noteIndices and locator are the main selection modes, but it does not clarify dry_run, groupIndex or trackIndex defaults, the singular noteIndex option, or how locator onset/pitch values are used for matching.

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 starts with the specific verb 'Delete', names the resource ('note(s)'), and scopes it to a group. It also names the two selection mechanisms, noteIndices and locator, which clearly distinguishes this removal tool from sibling get/update/add operations.

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 use case is implied: call this when notes should be removed from a group. However, the description does not explicitly say when not to use it, such as when notes should instead be updated, or mention prerequisites like locating notes with find_notes before deletion.

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