Skip to main content
Glama

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

Delete a cloned voice

tempolor_delete_cloned_voice
DestructiveIdempotent

Delete one cloned voice from its TemPolor account by clonedVoiceItemId (the account comes from the id), freeing a place under the plan's cap of saved voices. To remove a song use tempolor_delete_music; a MIDI file, tempolor_delete_midi. Answers result: true. Cannot be undone. DELETE /music/cloned-voices/{clonedVoiceItemId}.

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": {
      "clonedVoiceItemId": "<clonedVoiceItemId>"
    },
    "name": "tempolor_delete_cloned_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
clonedVoiceItemIdYesThe cloned voice to delete, e.g. user:12345-tempolor:<user_id>-voice:<itemId> (it names the account).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description adds rather than repeats: it discloses the quota side effect (one saved-voice slot freed), the return value ('Answers result: true'), and irreversibility ('Cannot be undone'). Only gap is no mention of failure modes (e.g. what happens with an unknown or in-use id), which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: action and identifier first, sibling routing second, side effects/return/endpoint last. No filler, and the endpoint path is a useful trailing anchor for an HTTP-backed tool.

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?

For a one-parameter destructive call with no output schema, everything an agent needs is present: what is deleted, how the account is resolved, that it is irreversible, and that it returns a boolean result. Nothing is left to guess.

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% and the schema already shows the compound id format, but the description adds a non-obvious inference: the account is derived from the id rather than passed separately. That matters given tempolor_list_accounts exists as a sibling and an agent might look for an accountId parameter.

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 cloned voice'), plus the identifier that scopes it ('by clonedVoiceItemId'), and names the two sibling delete tools it is not. An agent can separate it from tempolor_delete_music and tempolor_delete_midi 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?

Explicitly routes the agent: songs go to tempolor_delete_music, MIDI files to tempolor_delete_midi, which is exactly the decision an agent faces among the delete siblings. It also gives the motivating context ('freeing a place under the plan's cap of saved voices') so the tool's place in a workflow is clear.

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