Skip to main content
Glama

clear_curve

Removes all points from a curve or deletes points within a specified start/end tick range, letting you reset or trim pitch and expression curve data.

Instructions

Remove curve points (all, or between start and end ticks). / カーブの点を削除します(全部、または範囲内)

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>",
      "curve": "<curve>"
    },
    "name": "clear_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
partYes
pathNo
curveYes
startNo
trackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully discloses the deletion scope and the range semantics, but omits that this is a destructive, non-undoable mutation and what happens if the curve does not exist or start/end are omitted.

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?

Front-loaded, one compact sentence with the scope qualifier immediately after the verb. The bilingual duplication is conventional for this API rather than padding, so the text 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?

For a 6-parameter destructive mutation with no annotations, no output schema, and 0% schema coverage, the definition is thin: three parameters are undocumented and nothing explains failure behavior or reversibility. It answers what is deleted and how to scope it, but not enough to invoke confidently.

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

Parameters3/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 compensate. It explains start/end as tick bounds and implies curve identifies the target, but track, part, and path get no meaning at all — and path in particular is opaque without documentation.

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?

States a specific verb and resource: remove curve points, with the scope (all vs. a tick range) named. It is distinguishable from get_curve/set_curve in practice, though the text never explicitly contrasts itself with those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical clarifies the two operating modes (delete everything vs. delete within start/end), which tells an agent when to supply range args and when not to. There is no stated guidance on alternatives (e.g., use set_curve to overwrite instead of clearing) or on prerequisites.

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