Skip to main content
Glama

Kubeez

generate_separation

PRE-FETCH (mandatory): resources/read kubeez://skills/media-upload AND kubeez://skills/billing-confirmation. Separation is billed per-minute of audio — preview cost first.

Split an audio track into vocals + instrumental stems (MVSEP BS Roformer). Scope: generate:media. Billing: per-minute of audio duration, measured by the server; the audio must be a Kubeez upload. CANONICAL FLOW: (1) if the user has a local file, call get_upload_url(model_id='mvsep-40') and send the link. (2) when they confirm upload, call get_upload_session(token) — it returns total_audio_seconds. (3) call estimate(model='mvsep-40', reference_audio_seconds=<total_audio_seconds>) to get the exact price. (4) tell the user the price and ask for confirmation. (5) ONLY THEN call this tool. Don't charge silently. Required: media_url — a public HTTPS URL of the uploaded audio. Async: returns {separation_id, task_id, status: 'pending'} immediately. Poll get_status(separation_id) until status is 'completed'. When completed, the response carries vocals_url + instrumental_url (permanent CDN). For a full workflow with preview + library, direct the user to kubeez.com/audio/separation.

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": {
      "media_url": "<media_url>"
    },
    "name": "generate_separation"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare it is a non-read-only, open-world, non-idempotent call; the description adds the critical undocumented behavior — per-minute billing measured server-side, mandatory cost preview, mandatory skill pre-fetch, async pending response, polling requirement, and permanent CDN outputs. It also discloses the input constraint that the audio must be a Kubeez upload.

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?

Dense but well-sectioned — mandatory pre-fetch, purpose, scope, billing, canonical flow, parameter, async behavior — with no filler. It is long for a one-parameter tool, and the mandatory pre-fetch line competes with the purpose statement for the front-loaded position.

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?

Covers everything an agent needs for a billed async tool: prerequisites, cost-preview sequence, required input, return shape, polling loop, and final artifact URLs; the presence of an output schema means return values need no further explanation. Nothing material is missing.

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

Parameters5/5

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

Schema coverage is 0% and the single parameter has no schema description, so the description carries the full burden: media_url is described as 'a public HTTPS URL of the uploaded audio', plus the constraint that it must originate from a Kubeez upload. This adds real meaning beyond the bare string type.

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 precise verb+resource: "Split an audio track into vocals + instrumental stems (MVSEP BS Roformer)". It also names its scope (generate:media) and is clearly distinguishable from siblings like generate_music or generate_captions.

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?

Provides an explicit CANONICAL FLOW with numbered steps, names the prerequisite tools (get_upload_url, get_upload_session, estimate, get_status) and the exact conditions that select them. It also states a hard gate: 'ONLY THEN call this tool' after user confirms price.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources