Galatic.ai

Remix music

remix_music

Extend a track, cover an uploaded track, add vocals, or extend an upload. Spends Galatic.AI credits. Returns a job id; poll get_job_status with kind "music_remix".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "remix_music"
  }
}

Input Schema

Name	Required	Description
`model`	No
`style`	No
`title`	No
`action`	Yes
`prompt`	No
`audioId`	No
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`uploadUrl`	No
`continueAt`	No
`vocalGender`	No
`negativeTags`	No
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations declare the safety profile (non-readonly, non-destructive, non-idempotent), and the description adds two things annotations cannot: it spends Galatic.AI credits, and it is asynchronous, returning a job id that must be polled. It stops short of refund/failure behavior or per-action side effects.

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?

Two sentences, action list front-loaded, cost and follow-up compressed into a second clause. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, cost, and the async handoff for a 13-parameter mutation tool, which is the essential skeleton. What is missing is the parameter-to-action contract and error/credit-consumption behavior, which an agent needs to invoke this reliably.

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 coverage is only 23%, so the description must carry the load, yet it explains only the action enum implicitly. Ten parameters (audioId, uploadUrl, continueAt, vocalGender, negativeTags, style, prompt, title, model) get no explanation, and which inputs pair with which action is left entirely to inference.

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?

Names four specific operations (extend, cover an upload, add vocals, extend an upload) that map onto the action enum, and the resource is unambiguous. An agent can tell this apart from generate_music and extend_video without opening a schema.

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?

Gives a clear follow-up route ("poll get_job_status with kind 'music_remix'") but never says when to choose remix_music over generate_music or extend_video, nor which parameters each action requires. Usage is implied by the action list rather than stated.

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

All Galatic.ai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.