Skip to main content
Glama

get_curve

Retrieve a VOCALOID part curve's points, range, and default value for inspecting or editing pitch and expression data.

Instructions

Points, range and default of a part curve. / パートのカーブの点・範囲・既定値

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": "get_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
partYes
pathNo
curveYes
trackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden, and it discloses nothing about what happens on invalid track/part/curve, whether the curve must already exist, or what shape the returned data takes. There is also no output schema, so the return value (points, range, default) is named but never characterized.

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 single bilingual clause is efficient and front-loaded with the most important information, but the brevity crosses into under-specification rather than economy. Nothing is wasted, yet almost nothing is said.

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?

For a four-parameter tool with zero schema documentation, no annotations, and no output schema, the description should explain parameter roles and return structure. It supplies neither, leaving the agent to guess at identifiers and at the meaning of the returned 'range' and 'default'.

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

Parameters1/5

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

Schema description coverage is 0% across four parameters (track, part, curve, path), and the description adds no meaning to any of them. It never explains whether 'curve' is a name, ID, or index, whether 'part' and 'track' are zero- or one-based, or what 'path' addresses and why it is optional.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates what is returned (points, range, default) of a part curve, which lets an agent infer a read operation, but there is no explicit verb and no differentiation from the obvious siblings set_curve and clear_curve. The bilingual fragment is identifiable yet telegraphic rather than a clear statement of purpose.

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?

Nothing indicates when to call this instead of set_curve or clear_curve, nor any precondition (e.g., that a track/part must already exist). The agent must infer usage purely from the tool name and the read/write contrast with siblings.

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