Skip to main content
Glama

delete_notes

Removes specified notes from a VOCALOID6 track part by index, so you can clear unwanted notes before editing, playback, or export.

Instructions

Delete notes by index. / 番号で指定した音符を削除します

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": {
      "track": "<track>",
      "part": "<part>",
      "indexes": "<indexes>"
    },
    "name": "delete_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
partYes
pathNo
trackYes
indexesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It conveys that the operation is destructive, but says nothing about irreversibility, whether indexes refer to the list before or after prior deletions, what happens with out-of-range indexes, or whether an open project/session is required.

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 statement is short and front-loaded, which is good, but the second half is a verbatim Japanese translation that adds no information for most callers. It is efficiently sized yet under-specified rather than genuinely concise.

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?

With four parameters, 0% schema coverage, no annotations and no output schema, the description should explain track/part/path scoping and the deletion/undo model. It explains none of these, so an agent cannot call it correctly without inspecting the schema and guessing at semantics.

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%, so the description must explain all four parameters, but it only touches 'indexes' (and only loosely, as 'index'). The required 'track' and 'part' scoping parameters and the optional 'path' are entirely undefined, leaving the agent to guess whether indexes are globally unique or per-track/per-part.

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?

The description states a specific verb ('Delete') and resource ('notes') plus a selection mechanism ('by index'), which clearly separates it from add_notes, edit_notes and list_notes in the sibling set. It stops short of an explicit contrast with those siblings, but the operation is unambiguous.

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?

There is no guidance on when to use this versus edit_notes or remove_part, no preconditions (e.g. a project must be open, target track/part must exist), and no note about recovery or undo. The agent must infer all usage context from the name alone.

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