Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

get_track

Retrieve detailed information about a specific track in a REAPER project by its index number.

Instructions

Get detailed info for a single track by 0-based index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:83-89 (handler)
    The MCP tool registration and handler entry point for 'get_track'.
    @mcp.tool()
def get_track(track_index: int) -> dict[str, Any]:
    """Get detailed info for a single track by 0-based index."""
    try:
        return _wrap(adapter.get_track(track_index=track_index))
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/reaper_adapter.py:41-42 (helper)
    The adapter method that delegates the call to the underlying Reaper client.
    def get_track(self, track_index: int) -> dict[str, Any]:
    return self._client.call("get_track", track_index=track_index)

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only discloses the indexing scheme (0-based). It omits error behavior (out-of-bounds handling), return structure details despite having an output schema, and side effects (though 'Get' implies read-only, explicit confirmation would help).

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?

Single sentence wastes no words and leads with the verb. However, given the complexity (48+ sibling tools in a DAW domain) and 0% schema coverage, the extreme brevity leaves significant gaps that additional structured sentences could have addressed without violating conciseness principles.

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?

Inadequate for a complex audio production domain. With zero input schema descriptions and numerous sibling track operations, the description should clarify relationships (e.g., 'use after list_tracks'), valid index sourcing, and domain-specific constraints. Output schema existence mitigates need to describe returns, but input guidance is insufficient.

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?

Adds critical '0-based' semantic information entirely missing from the 0% coverage schema, explaining the nature of track_index. However, fails to compensate for lack of schema descriptions regarding valid ranges (0 to N-1?), bounds checking, or whether index refers to visual order or creation order.

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?

Clear verb (Get) and resource (track) with specific scope (detailed info, single track). The '0-based index' qualifier helps distinguish from bulk retrieval (list_tracks) and name-based lookup, though 'detailed info' remains somewhat vague.

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?

No explicit guidance on when to use this versus list_tracks or get_track_items. The '0-based index' hints at the addressing scheme but doesn't clarify prerequisite steps (e.g., obtaining valid indices from list_tracks) or error conditions for invalid indices.

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