Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

get_envelope_points

Extract automation envelope points from REAPER track envelopes to access time, value, shape, and tension data for audio parameter control.

Instructions

Read all automation envelope points from a track 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. Returns envelope name and list of points with time, value, shape, tension.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
envelope_indexNo
envelope_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:986-1008 (handler)
    The MCP tool handler function for 'get_envelope_points', which registers the tool and calls the adapter.
    @mcp.tool()
def get_envelope_points(
    track_index: int,
    envelope_index: int | None = None,
    envelope_name: str | None = None,
) -> dict[str, Any]:
    """
    Read all automation envelope points from a track 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.
    Returns envelope name and list of points with time, value, shape, tension.
    """
    try:
        return _wrap(
            adapter.get_envelope_points(
                track_index=track_index,
                envelope_index=envelope_index,
                envelope_name=envelope_name,
            )
        )
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/reaper_adapter.py:534-542 (handler)
    The adapter implementation that communicates the 'get_envelope_points' request to the underlying REAPER bridge.
    def get_envelope_points(
    self, track_index: int, envelope_index: int | None = None, envelope_name: str | None = None
) -> dict[str, Any]:
    return self._client.call(
        "get_envelope_points",
        track_index=track_index,
        envelope_index=envelope_index,
        envelope_name=envelope_name,
    )

Tool Definition Quality

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses output structure (time, value, shape, tension) and important REAPER-specific visibility constraint. However, lacks explicit read-only safety confirmation, error conditions, or side effects beyond the visibility note.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three efficient, front-loaded sentences. Opens with purpose, followed by parameter identification guidance, then preference rationale and return value summary. Zero redundancy despite 0% schema coverage burden.

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?

Given output schema exists, the summary of return values is sufficient. Despite complete lack of schema descriptions, the tool provides enough context for correct invocation including track indexing and envelope identification strategies.

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?

With 0% schema description coverage, description effectively compensates by providing concrete name examples ('Volume', 'Pan', 'Mute'), noting '0-based' indexing, and explaining the relationship/preference between envelope_name and envelope_index parameters.

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?

States specific verb 'Read' with resource 'automation envelope points' and distinguishes clearly from mutation siblings like 'clear_envelope_points' and 'insert_envelope_point' by scope (all points vs single) and action.

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?

Explicitly documents two identification methods (name vs index) and provides clear preference: 'Using envelope_name is preferred'. Explains specific UI constraint workaround that name 'works even if the envelope is not yet visible/armed'.

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