Skip to main content
Glama

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

Create an instrumental

tempolor_create_instrumental

Generate an instrumental track (no vocals) with TemPolor's current instrumental model from a prompt, optionally in the key, tempo and chord progression you set; for a song with vocals use tempolor_create_song. A track counts against the plan's monthly tracks on Lite and Pro; Ultra has no monthly count but can be limited to about 300 songs a day per account; a 429 means the accounts are busy (tempolor_list_running_jobs). Waits up to ~50 s and returns the job_id, status and, once COMPLETED, a temporary mp3 url; else call tempolor_get_music. POST /music/instrumental.

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": {
      "prompt": "<prompt>"
    },
    "name": "tempolor_create_instrumental"
  }
}

Input Schema

NameRequiredDescriptionDefault
bpmNoThe tempo in beats per minute, 50-190.
waitNoWait up to ~50 s for the track to finish (default true); false returns the job_id at once.
chordsNoA chord progression, as C F G Am. Up to 200 characters.
promptYesWhat the instrumental is: genre, mood, instruments. Up to 2,000 characters.
maxJobsNoThe most jobs the account may run at once for this request, from 1. Default: the account's maxJobs (tempolor_list_accounts).
user_idNoThe TemPolor account (user_id from tempolor_list_accounts) to run on. Omit to use a healthy account with a free maxJobs slot.
replyRefNoYour own reference, included in every callback. Up to 1,024 characters.
replyUrlNoA callback URL that receives a POST with the job's tempolor_get_music record while the track is made and once it ends; a job not done within 60 minutes ends with code 408. Up to 1,024 characters.
tonalityNoThe key, as C:major or F#:minor.
model_instrumentalNoThe same values as the REST API; omit it for TemPolor's current instrumental model. Models: https://useapi.net/docs/api-tempolor-v1#models.i4

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a non-readOnly, open-world, non-idempotent but non-destructive operation. The description goes well beyond that with quota semantics by plan (monthly count on Lite/Pro, ~300/day on Ultra), the meaning of a 429, and the wait/return behavior including a temporary mp3 url. It stops short of describing what happens to quota on failed jobs or whether the temporary url expires, so it is not fully exhaustive.

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?

Purpose is front-loaded in the first clause, followed by the sibling route, quota rules, and return behavior in a logical order. It is dense with semicolons and reads as a single long paragraph, but essentially every clause carries operational information an agent needs.

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?

With 10 parameters and no output schema, the description supplies what the schema cannot: initial return values (job_id, status, mp3 url once COMPLETED), the ~50 s wait ceiling with a polling fallback, the plan-dependent quota model, and callback timeout behavior (408 after 60 minutes). Nothing essential for correct invocation is missing.

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 description coverage is 100%, so every parameter (bpm, chords, tonality, model_instrumental, wait, user_id, maxJobs, replyUrl, replyRef) is already documented in the schema. The description only adds framing that key, tempo and chords are optional and that wait defaults to ~50 s, which restates rather than extends the schema. Baseline 3 applies when the schema carries the semantic load.

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 specific verb and resource ("Generate an instrumental track (no vocals)") plus the model used, and explicitly distinguishes itself from tempolor_create_song for vocal tracks. The endpoint notation POST /music/instrumental confirms the operation unambiguously.

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 for vocal songs (tempolor_create_song), tells the agent what to do on a 429 (tempolor_list_running_jobs), and what to do if the track isn't ready within the wait window (tempolor_get_music). These are explicit routing rules tied to observable conditions rather than vague suggestions.

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