Skip to main content
Glama

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

List MIDI files

tempolor_list_midi
Read-onlyIdempotent

List the MIDI files uploaded to one TemPolor account (tempolor_upload_midi or the TemPolor web app): midiItemId (pass it to tempolor_create_song), name, midiUrl and opType. Pages: pass the cursor of the answer while hasNext is true. GET /music/midi.

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_list_midi"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoThe cursor of the previous page, to read the next one. Omit for the first page.
user_idNoThe TemPolor account (user_id from tempolor_list_accounts) to list. Required when you have several TemPolor accounts; with one it may be left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds behavior the annotations cannot: pagination termination via hasNext, account scoping when multiple accounts exist, and the four fields returned in each item. It does not state rate limits or ordering of results.

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?

Three tight sentences, front-loaded with the resource and scope, then the returned fields and pagination rule. Every clause carries information; the trailing transport note 'GET /music/midi' is the only low-value fragment.

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?

There is no output schema, and the description compensates by enumerating the returned item fields and the field to pass downstream. Together with the pagination rule and the optional-account semantics, an agent has what it needs to call this correctly in a single turn.

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 schema documents both parameters and the baseline would be 3. The description adds the pagination loop condition ('pass the cursor of the answer while hasNext is true'), which is not expressed in the schema, and reinforces the user_id/'one account' relationship.

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 ('List the MIDI files') and immediately scopes it to one TemPolor account, naming the sibling that produces them (tempolor_upload_midi) plus the web app. An agent can separate this from upload/delete/create_song tools without opening any 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?

Explains the context of use (retrieving files uploaded via tempolor_upload_midi or the web app) and the downstream step (pass midiItemId to tempolor_create_song), which is actionable routing guidance. It stops short of an explicit when-not statement, but no competing list tool for MIDI exists among the siblings, so the gap is minor.

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