Skip to main content
Glama

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

Delete a MIDI file

tempolor_delete_midi
DestructiveIdempotent

Delete one uploaded MIDI file from its TemPolor account by midiItemId; the account comes from the id. To remove a song use tempolor_delete_music; a cloned voice, tempolor_delete_cloned_voice. Answers result: true. Cannot be undone. DELETE /music/midi/{midiItemId}.

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": {
      "midiItemId": "<midiItemId>"
    },
    "name": "tempolor_delete_midi"
  }
}

Input Schema

NameRequiredDescriptionDefault
midiItemIdYesThe MIDI file to delete, e.g. user:12345-tempolor:<user_id>-midi:<itemId> (it names the account).

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 destructiveHint, idempotentHint and readOnlyHint=false, but the description adds value on top: 'Cannot be undone' spells out irreversibility in plain terms, and 'Answers result: true' discloses the return shape despite there being no output schema. It does not cover permission/auth requirements, which is the only notable omission.

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?

Front-loaded with the destructive action and scope, then alternatives, then return/irreversibility facts — every clause carries information. It is telegraphic to the point of terseness ('Answers result: true'), but nothing is filler.

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?

For a single-parameter destructive tool with no output schema, the description covers scope, alternatives, irreversibility and return value, which is essentially everything needed to invoke it safely. Only the authorization context is absent.

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% and the schema property already explains that the id encodes the account, so 'the account comes from the id' largely restates structured data. Baseline 3 applies since the schema carries the parameter burden.

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 ('Delete one uploaded MIDI file ... by midiItemId') and explicitly disambiguates from siblings: tempolor_delete_music for songs, tempolor_delete_cloned_voice for cloned voices. An agent can route to this tool 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the two alternative delete tools and the object each one handles, which is exactly the routing decision an agent faces in this sibling set. The endpoint line reinforces the scope (MIDI-only resource).

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