Skip to main content
Glama

get_project_info

Retrieve current project name, path, tempo, track count, and length to monitor and manage project state.

Instructions

Get information about the current project: name, path, tempo, tracks, length.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The get_project_info() handler function that retrieves current project info (name, path, tempo, time signature, length, track count, markers, regions) via reapy, registered as an MCP tool via @mcp.tool() decorator.
    def get_project_info() -> dict:
        """Get information about the current project: name, path, tempo, tracks, length."""
        try:
            project = get_project()
            markers = []
            try:
                for i in range(project.n_markers):
                    m = project.markers[i]
                    markers.append({"index": i, "name": m.name, "position": m.position})
            except Exception:
                pass
    
            regions = []
            try:
                for i in range(project.n_regions):
                    r = project.regions[i]
                    regions.append({"index": i, "name": r.name, "start": r.start, "end": r.end})
            except Exception:
                pass
    
            return {
                "success": True,
                "name": project.name,
                "path": project.path,
                "tempo": project.bpm,
                "time_signature": f"{project.time_signature[0]}/{project.time_signature[1]}",
                "length": project.length,
                "track_count": project.n_tracks,
                "markers": markers,
                "regions": regions,
            }
        except Exception as e:
            logger.error(f"get_project_info failed: {e}")
            return {"success": False, "error": str(e)}
  • The register_tools function that defines get_project_info as an MCP tool using the @mcp.tool() decorator inside the registration function.
    def register_tools(mcp):
    
        @mcp.tool()
  • Server imports register_tools from project_tools (as _reg_project) and calls it on line 20 to register the tool with the FastMCP server.
    from reaper_mcp.project_tools import register_tools as _reg_project
    from reaper_mcp.track_tools import register_tools as _reg_track
    from reaper_mcp.midi_tools import register_tools as _reg_midi
    from reaper_mcp.fx_tools import register_tools as _reg_fx
    from reaper_mcp.audio_tools import register_tools as _reg_audio
    from reaper_mcp.mixing_tools import register_tools as _reg_mixing
    from reaper_mcp.render_tools import register_tools as _reg_render
    from reaper_mcp.mastering_tools import register_tools as _reg_mastering
    from reaper_mcp.analysis_tools import register_tools as _reg_analysis
    
    _reg_project(mcp)
    _reg_track(mcp)
    _reg_midi(mcp)
    _reg_fx(mcp)
    _reg_audio(mcp)
    _reg_mixing(mcp)
    _reg_render(mcp)
    _reg_mastering(mcp)
    _reg_analysis(mcp)
  • The get_project() helper function used by get_project_info to obtain a reapy.Project instance, ensuring connection to REAPER first.
    def get_project() -> reapy.Project:
        ensure_connected()
        return reapy.Project()
  • The return schema/dict shape for get_project_info containing success, name, path, tempo, time_signature, length, track_count, markers, regions (or error).
        return {
            "success": True,
            "name": project.name,
            "path": project.path,
            "tempo": project.bpm,
            "time_signature": f"{project.time_signature[0]}/{project.time_signature[1]}",
            "length": project.length,
            "track_count": project.n_tracks,
            "markers": markers,
            "regions": regions,
        }
    except Exception as e:
        logger.error(f"get_project_info failed: {e}")
        return {"success": False, "error": str(e)}
Behavior3/5

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

No annotations exist, so description carries full burden. It states a read operation with no side effects, but does not mention prerequisites (e.g., project must be open) or error cases. Adequate but leaves some uncertainty.

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?

One sentence, no waste, front-loaded with action and resource. Every word earns its place.

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?

For a zero-parameter tool with no output schema and no annotations, the description covers purpose and output fields. Could mention more details like units or format, but this is sufficient.

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?

No parameters, so baseline is 4. The description adds value by enumerating the data fields returned, which is not in the input 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 specifies the verb 'Get' and the resource 'current project', and lists the exact information returned (name, path, tempo, tracks, length). This clearly distinguishes it from sibling tools like 'create_project' or 'get_track_info'.

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

Usage Guidelines3/5

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

Usage context is implied: use when needing generic project information. No explicit guidance on when to avoid or alternatives, but given the tool's simplicity, this is minimally adequate.

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/bonfire-audio/reaper-mcp'

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