Skip to main content
Glama
rosasynthesiz

Logic Pro MCP

by rosasynthesiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

logic_deliver

Bounce a Logic Pro project to finished audio, verify the files, upload them to your own cloud storage, and return share links for delivery.

Instructions

Get finished audio out of Logic and into cloud storage.

bounce_and_upload - the whole chain: render the project to `formats`, verify the files, upload them,
                    and return share links. Give directory + filename + formats + folder.
upload            - push existing local `paths` to remote:folder.
remotes / list    - what storage is configured, and what is already in a folder.
setup             - how the user connects their OWN cloud account.

Uploads go to the user's own remote: this server ships no credentials and no default account. The
remote comes from `remote`, else $LOGIC_MCP_REMOTE, else the single configured remote; with several
configured and nothing pinned it refuses rather than guessing. Run `setup` for the exact commands —
the user runs them themselves, since the flow ends in a browser sign-in to their own account.

Input Schema

NameRequiredDescriptionDefault
pathsNo
actionYes
folderNo
remoteNo
end_barNo
formatsNo
timeoutNo
filenameNo
directoryNo
start_barNo
make_linksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that uploads go to the user's own remote, that the server ships no credentials or default account, the remote resolution precedence and refusal on ambiguity, and that setup ends in a browser sign-in run by the user. Lacks details on overwrite behavior, rate limits, and upload failure handling.

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?

Front-loads the purpose, then gives a structured action breakdown, remote behavior, and setup note. The length is justified by five distinct actions, though the indented inline list and repeated framing could be tightened slightly.

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?

The tool is complex: eleven parameters, five actions, no annotations, no output schema, and no schema descriptions. The description covers action routing and some auth context, but leaves many parameters and most return/error behavior undocumented, making it insufficient for fully reliable invocation.

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

Parameters2/5

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

Schema description coverage is 0% across 11 parameters, so the description must compensate. It mentions directory, filename, formats, folder, paths, and remote, but leaves start_bar, end_bar, timeout, make_links, and the precise semantics/values of the named parameters unexplained. An agent must infer heavily from raw schema defaults and types.

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 a specific verb and resource: 'Get finished audio out of Logic and into cloud storage.' The action list further distinguishes five concrete sub-purposes (bounce_and_upload, upload, remotes/list, setup). It does not explicitly differentiate itself from the sibling logic_export, which is the only missing element.

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?

Explains when to use each action: bounce_and_upload for the full render/upload chain, upload for existing local paths, remotes/list for inspecting configured storage, and setup for connecting the user's own cloud account. Also gives the remote resolution rule and refusal behavior. No explicit when-not guidance relative to sibling tools.

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