Skip to main content
Glama

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

Get a track

tempolor_get_music
Read-onlyIdempotent

One song or instrumental by job_id (from tempolor_create_song, tempolor_create_instrumental or tempolor_list_music): status (0-9 GENERATING, 10-29 FAILED, 30+ COMPLETED), status_name, status_final, progress, title, cover and musical details, and once COMPLETED a temporary mp3 url. wait: true waits up to ~50 s for a track still generating; call again until status_final is true. A job just submitted can read as not listed by TemPolor yet for up to 10 minutes; that is not a failure, call again (wait: true). An unknown or deleted job_id answers 404. GET /music/{job_id}.

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": {
      "job_id": "<job_id>"
    },
    "name": "tempolor_get_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the track to finish (default false: one read).
job_idYesThe job_id to read, e.g. user:12345-tempolor:<user_id>-job:<itemId> (it names the account).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/non-destructive; the description adds what annotations cannot — status code banding (0-9 generating, 10-29 failed, 30+ completed), the temporary nature of the mp3 url, the eventual-consistency lag of up to 10 minutes, and 404 semantics for unknown or deleted job_ids. That is genuinely useful behavior beyond the structured fields.

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, and the subsequent sentences cover status bands, polling, edge case, and error case without filler. The first sentence is a dense run-on listing return fields, but no sentence is expendable.

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 no output schema, the description carries the burden of describing return values and does so thoroughly, plus it explains polling semantics and the 404 case. An agent has everything needed to call this correctly and interpret results on the first attempt.

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 job_id format and the wait default are already documented structurally. The description reinforces what wait does in practice ("call again until status_final is true") but adds little new meaning to the parameter definitions themselves; the status-band detail describes return values, not inputs.

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?

"One song or instrumental by job_id" gives a specific resource (a single track) and read intent, and explicitly names the sibling tools that produce the job_id. It also enumerates the payload (status, status_name, progress, title, cover, musical details, mp3 url), so an agent can tell this apart from the list/delete/download siblings immediately.

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?

Strong operational guidance: wait:true with ~50 s timeout, retry until status_final is true, and the important caveat that a fresh job may be unlisted for up to 10 minutes and should be re-polled rather than treated as failed. It stops short of explicitly routing multi-track reads to tempolor_list_music, so 4 rather than 5.

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