Skip to main content
Glama

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

Upload a MIDI file

tempolor_upload_midi

Upload a MIDI file (audio/midi or audio/x-midi, under 5 MB) to a TemPolor account, to build songs on: returns midiRenderVO with midiItemId (pass it to tempolor_create_song, which then runs on that account), name and midiUrl, ready at once. A MIDI file cannot be combined with a voice in one song. Uploaded files are listed by tempolor_list_midi. POST /music/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": {
      "name": "<name>"
    },
    "name": "tempolor_upload_midi"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA public https URL of the MIDI file.
nameYesA name for the MIDI file (.mid is added when missing).
user_idNoThe TemPolor account (user_id from tempolor_list_accounts) to upload to. 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 MIDI file's content, base64-encoded (instead of url; small files).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, open-world write; the description adds real context beyond them — a 5 MB size ceiling, the accepted MIME types, the fact the render is 'ready at once' (i.e., no polling job), and the exact return shape (midiItemId, name, midiUrl) without an output schema. It does not address duplicate uploads or failure modes, so it is not a full 5.

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?

The core action and its constraints are front-loaded in the first clause, and every following clause adds a distinct fact (size, return fields, downstream call, incompatibility, listing tool, endpoint). It is dense to the point of being run-on, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 usefully documents the returned midiRenderVO fields and that the result is immediately available, plus the size/type constraints and the follow-up tool. What remains uncovered is edge behavior — what happens on duplicate names or failed uploads — which is a minor gap for this complexity.

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 the baseline is 3; the schema already explains url vs contentBase64, the mimeType requirement pairing, the .mid suffix behavior on name, and user_id's multi-account condition. The description only echoes the size limit and the fact that midiItemId is the reusable handle, adding little parameter meaning beyond structured fields.

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 (upload a MIDI file) plus the target (a TemPolor account), the underlying endpoint (POST /music/midi), and distinguishes itself from siblings by naming tempolor_create_song as the consumer and tempolor_list_midi as the lister. An agent can identify this tool without opening the schema.

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?

Gives clear downstream context: the returned midiItemId is what you pass to tempolor_create_song, and the resulting song runs on that account. It also states an exclusion (a MIDI file cannot be combined with a voice in one song) and points at tempolor_list_midi for the uploaded set. It stops short of explicitly contrasting url vs contentBase64 upload paths or naming when not to upload at all.

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