Skip to main content
Glama

insert_envelope_point

Add automation points to REAPER envelopes for precise control of volume, pan, mute, and other parameters in audio projects.

Instructions

Insert a point into an automation envelope. Identify the envelope by name (e.g. 'Volume', 'Pan', 'Mute') or by 0-based envelope_index. Using envelope_name is preferred and works even if the envelope is not yet visible/armed in the REAPER UI.

  • time: position in seconds

  • value: linear amplitude (Volume: 0.0=silence, 1.0=0 dB, 2.0=+6 dB max)

  • shape: 0=linear, 1=square, 2=slow start/end, 3=fast start, 4=fast end, 5=bezier

  • tension: bezier tension (-1.0 to 1.0)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
timeYes
valueYes
envelope_indexNo
envelope_nameNo
shapeNo
tensionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler that registers 'insert_envelope_point' and calls the adapter.
    def insert_envelope_point(
        track_index: int,
        time: float,
        value: float,
        envelope_index: int | None = None,
        envelope_name: str | None = None,
        shape: int = 0,
        tension: float = 0.0,
    ) -> dict[str, Any]:
        """
        Insert a point into an automation envelope.
        Identify the envelope by name (e.g. 'Volume', 'Pan', 'Mute') or by
        0-based envelope_index. Using envelope_name is preferred and works even
        if the envelope is not yet visible/armed in the REAPER UI.
        - time: position in seconds
        - value: linear amplitude (Volume: 0.0=silence, 1.0=0 dB, 2.0=+6 dB max)
        - shape: 0=linear, 1=square, 2=slow start/end, 3=fast start, 4=fast end, 5=bezier
        - tension: bezier tension (-1.0 to 1.0)
        """
        try:
            return _wrap(
                adapter.insert_envelope_point(
                    track_index=track_index,
                    envelope_index=envelope_index,
                    envelope_name=envelope_name,
                    time=time,
                    value=value,
                    shape=shape,
                    tension=tension,
                )
            )
  • The adapter method that forwards the 'insert_envelope_point' request to the REAPER client.
    def insert_envelope_point(
        self,
        track_index: int,
        envelope_index: int | None = None,
        envelope_name: str | None = None,
        time: float = 0.0,
        value: float = 1.0,
        shape: int = 0,
        tension: float = 0.0,
    ) -> dict[str, Any]:
        return self._client.call(
            "insert_envelope_point",
            track_index=track_index,
            envelope_index=envelope_index,
            envelope_name=envelope_name,
            time=time,
            value=value,
            shape=shape,
            tension=tension,
        )
Behavior4/5

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

No annotations provided, so description carries full behavioral burden. Adds crucial REAPER-specific context: visibility/arming requirements, linear amplitude scaling (including dB mapping for Volume), and shape interpolation semantics. Does not disclose error behavior or idempotency.

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?

Well-structured with clear front-loaded purpose sentence followed by identification logic and parameter bullets. Efficient use of space explaining domain-specific enums (shape codes) and value ranges without verbosity.

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

Completeness4/5

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

Appropriately complete for a 7-parameter specialized audio tool with empty schema. Covers critical domain knowledge (envelope arming, dB mapping, interpolation shapes) that schema cannot express. Output schema exists, so omission of return value details is acceptable.

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

Parameters4/5

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

Schema has 0% description coverage (titles only). Description compensates by detailing 6 of 7 parameters: time (seconds), value (amplitude/dB mapping), envelope identifiers (name preference, 0-based index), shape (enum mapping), and tension (range). Omits semantics for track_index (0-based? master track?).

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 specific action (Insert) and resource (automation envelope point). Clarifies two methods of envelope identification (name vs 0-based index). Implies temporal domain (seconds) which distinguishes from sibling 'insert_envelope_point_at_beat', though it does not explicitly name that alternative.

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?

Provides explicit internal guidance: 'Using envelope_name is preferred and works even if the envelope is not yet visible/armed in the REAPER UI.' This clarifies selection between envelope_name and envelope_index parameters. However, lacks explicit cross-tool guidance distinguishing from 'clear_envelope_points' or 'get_envelope_points'.

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/danielkinahan/ReaMCP'

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