Galatic.ai

Generate MIDI

generate_midi

Transcribe a separated track to MIDI. taskId is required: pass the completed stem-separation task id from separate_stems. The route returns 400 without it, and an audioUrl alone is not enough. Spends Galatic.AI credits. Returns a job id; poll get_job_status with kind "midi".

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "generate_midi"
  }
}

Input Schema

Name	Required	Description
`taskId`	No	Required. The completed stem-separation task id from separate_stems.
`audioId`	No	Library audio id for the track, when it is in your library.
`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."
`audioUrl`	No	Audio URL. Accepted, but the route still requires taskId.
`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.
`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.

Changed3 schema fields changedOct 27, 2026

addedInput schema / properties / audioId / description

Added value: +"Library audio id for the track, when it is in your library."

addedInput schema / properties / audioUrl / description

Added value: +"Audio URL. Accepted, but the route still requires taskId."

addedInput schema / properties / taskId / description

Added value: +"Required. The completed stem-separation task id from separate_stems."

First observedOct 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond annotations, it discloses important behavior: the call spends credits, returns a job id rather than final MIDI directly, and requires polling get_job_status with kind "midi". It also warns that omission of taskId causes a 400, which is useful operational context.

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?

The description is four tight sentences, front-loaded with the core action and immediately followed by the critical prerequisite and follow-up behavior. Every sentence carries operational value with little waste.

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?

For a non-readonly, non-idempotent job-creating tool with no output schema, the description supplies the essential prerequisites, cost implication, validation behavior, return shape, and polling path. The remaining parameter details are fully covered by the schema.

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?

Schema coverage is 100%, so parameter meanings are already largely documented. The description reinforces taskId's importance and the insufficiency of audioUrl alone, but mostly repeats schema-level information rather than adding new semantics for the other parameters.

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 states a specific verb and resource: "Transcribe a separated track to MIDI." It makes the tool distinguishable from music-generation siblings by tying it to separated-track input and MIDI output, not general audio generation.

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?

It clearly states the prerequisite: pass taskId from separate_stems, and warns that audioUrl alone is insufficient. It also explains the follow-up workflow via get_job_status, though it does not explicitly contrast against all alternative generation tools.

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.