Skip to main content
Glama
wretcher207

Reaper Daemon

by wretcher207
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_midi_inputs

Read-only

Lists MIDI input devices detected by REAPER, providing index, name, availability, and configurability. Use it to locate a device index before configuring inputs.

Instructions

Read-only: list the MIDI input devices REAPER can see. Takes no arguments. Returns {inputs: [{index, name, available, configurable}], all_devices: 63, virtual_keyboard: 62}. Call this before configure_midi_input to find a device index; configurable is false for indices above 63, which configure_midi_input cannot set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv3.21.0
    • removedInput schema / properties / dry_run
      Removed value: -{
-  "description": "Preview: return what would run without changing the project.",
-  "type": "boolean"
-}
    • removedInput schema / properties / fx_guid
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / fx_index
      Removed value: -{
-  "type": "integer"
-}
    • removedInput schema / properties / fx_name_contains
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / fx_scope
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / target_track_guid
      Removed value: -{
-  "description": "Stable REAPER track GUID; preferred when available.",
-  "type": "string"
-}
    • removedInput schema / properties / track
      Removed value: -{
-  "description": "Exact track name (case-insensitive).",
-  "type": "string"
-}
    • removedInput schema / properties / track_contains
      Removed value: -{
-  "description": "Case-insensitive substring; errors if it matches more than one track.",
-  "type": "string"
-}
    • removedInput schema / properties / use_selected_track
      Removed value: -{
-  "description": "Target the currently selected track instead of naming one.",
-  "type": "boolean"
-}
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already provide readOnlyHint=true, and the description reinforces that with 'Read-only.' It goes beyond the annotation by disclosing the exact return shape, the fixed magic numbers 63 and 62, and the behavioral meaning of configurable=false for high indices. This gives the agent concrete expectations without requiring an output schema.

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 sentences, each earning its place: purpose and read-only nature, return shape, and the actionable relationship to configure_midi_input. It front-loads the key behavior and packs important constraints into a compact, readable definition.

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 no output schema, the description fully specifies the return value structure and the special index semantics. It covers how the result should be used with a sibling tool, which is the main context needed for a zero-argument read-only listing tool. Nothing an agent needs to call this correctly is missing.

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?

The tool takes zero parameters, and the input schema is already empty. The description explicitly states 'Takes no arguments,' which removes any doubt about parameter semantics. With 100% schema coverage and no parameters to explain, the description adds appropriate confirmation without needing more.

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 a specific verb and resource: list the MIDI input devices REAPER can see. Clearly distinguishes itself from the sibling configure_midi_input by framing itself as the read-only lookup step and explicitly noting the device-index contract. Even without opening the schema, an agent knows exactly what this tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs when to call the tool: 'Call this before configure_midi_input to find a device index.' It also provides a constraint on usage by explaining that configurable is false above index 63 and that configure_midi_input cannot set those. This is clear routing guidance with no ambiguity.

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

Deploy Server

Other Tools