Skip to main content
Glama

envelope_add_points

Insert automation points into a track or FX parameter envelope, supporting point shapes and tension. Create the envelope if needed.

Instructions

Batch-insert automation points into an envelope.

Point shape codes: 0=linear, 1=square, 2=slow start/end, 3=fast start, 4=fast end, 5=bezier. Tension -1 to +1 for curve skew.

Value units:

  • Volume track env: linear gain where 1.0 = unity (0 dB), 2.0 ≈ +6 dB, 0.5 ≈ -6 dB. Use 10**(db/20) to convert from dB.

  • Pan: -1.0 (hard left) to +1.0 (hard right).

  • Mute: 0.0 or 1.0.

  • FX params: 0.0-1.0 normalized (same as fx_set_param).

Args: track_index: Track. points: JSON array of {"time":s, "value":v, "shape":0, "tension":0}. envelope_name: Track envelope name (ignored with FX param). fx_index / param_index: Target FX param envelope (-1 for track env). create: If the envelope doesn't exist yet, create it (default True).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
pointsYes
envelope_nameNoVolume
fx_indexNo
param_indexNo
createNo
Behavior3/5

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

No annotations provided, so the description carries full burden. It explains input semantics and value conversions but does not disclose side effects like whether points are appended or replaced, limits, or error conditions. This is adequate but not comprehensive.

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 well-structured with sections but somewhat verbose. It front-loads the main purpose and uses clear formatting, though could be trimmed slightly without losing clarity.

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

Completeness5/5

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

Despite having 6 parameters and no output schema, the description covers all parameters, input format, special value conventions for volume/pan/mute/FX, and the create parameter. It is nearly complete for effective tool usage.

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

Parameters5/5

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

The schema has 0% description coverage, so the description compensates fully. It explains the JSON array format, shape codes with meanings, value units for different envelope types, and the purpose of each parameter, adding substantial meaning beyond the schema.

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 clearly states 'Batch-insert automation points into an envelope.' It uses a specific verb ('batch-insert') and resource ('automation points'), and distinguishes from sibling tools like envelope_clear_range and envelope_get_points.

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 description provides context on when to use (e.g., for various envelope types) but does not explicitly state when not to use or compare to alternatives. It does explain the parameter meanings thoroughly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xDarkzx/Reaper-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server