Skip to main content
Glama

TemPolor MCP Server by useapi.net (third-party)

Split your audio into stems

tempolor_split_stems

Split your own audio file (MP3, WAV, M4A or FLAC, up to 50 MB through this server) into vocal and instrument stems and return stemsZipUrl, a ZIP of them; for a track made here use tempolor_download_music with file_format stems instead. Stem splitting is on TemPolor Pro and Ultra, with no per-split charge. The REST waits up to 120 s for the ZIP but this tool answers within about a minute, and the ZIP link comes only in that answer: for long files call POST /music/stems-splitter directly. POST /music/stems-splitter.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tempolor_split_stems"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA public https URL of the audio file.
user_idNoThe TemPolor account (user_id from tempolor_list_accounts) to split on. Required when you have several TemPolor accounts; with one it may be left out.
mimeTypeNoThe file's type. Required with contentBase64. With url the default is the url's answer, else its file extension.
contentBase64NoThe audio file's content, base64-encoded (instead of url; small files).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the generic readOnly/openWorld/idempotent/destructive profile; the description goes well beyond them with a 50 MB size cap, the accepted formats, plan entitlement, billing behavior, and the crucial timing caveat that this tool answers in about a minute while the REST path waits 120 s. It also discloses that the ZIP link is returned only in that answer, which is a non-obvious behavioral constraint an agent must not miss.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the piece reads in one dense breath, but the tail repeats the endpoint already named a sentence earlier as a dangling fragment ("POST /music/stems-splitter."), which is pure waste. The timing passage is also internally tense, pairing "up to 120 s" for REST against "about a minute" for this tool without reconciling them.

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 job-spawning tool with no output schema, the description covers the size limit, formats, plan gating, cost, timeout behavior, and the fallback endpoint, plus where the returned link lives. An agent could call this correctly and know when not to without consulting anything else.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds real constraint information not present in the schema: the 50 MB ceiling and the accepted audio formats (MP3/WAV/M4A/FLAC) that map onto the mimeType enum and contentBase64. It does not clarify the url-versus-contentBase64 trade-off beyond what the schema already says about small files.

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 opening clause names a specific verb and resource ("Split your own audio file ... into vocal and instrument stems") and states the concrete return value (stemsZipUrl, a ZIP). It also explicitly distinguishes itself from the sibling case, directing agents to tempolor_download_music with file_format stems for tracks made on the platform.

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?

Names the alternative tool and the exact condition that selects it ("for a track made here use tempolor_download_music with file_format stems instead"), and adds a second routing rule: for long files bypass this tool and call POST /music/stems-splitter directly. Plan gating (Pro and Ultra) and the absence of per-split charge further qualify when this is callable.

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