Skip to main content
Glama
Sign In

Galatic.ai

by ai.galatic
OverviewDiscussionsAdmin

Delete voice clone

delete_voice_clone
Destructive

Delete one cloned voice by voiceId (from list_voice_clones). For a voice you own this is permanent: it is removed from the voice provider and from your library, and cannot be restored. A voice shared with you removes only your access; the owner keeps it. A voiceId the caller holds no record for is a 404.

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": {
      "voiceId": "<voiceId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "delete_voice_clone"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
voiceIdYesvoiceId from list_voice_clones.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / voiceId / description
      Added value: +"voiceId from list_voice_clones."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=false, but the description adds far more: exact consequences (removed from provider and library, cannot be restored), a differentiated behavior for shared voices (only your access is removed), and the 404 response for unknown ids. This is meaningful added context beyond 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.

Conciseness5/5

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

Four tight sentences ordered from purpose to consequence to edge case to error behavior. Every sentence carries information an agent would otherwise have to assume.

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 destructive single-item deletion with no output schema, the description covers the irreversible outcome, the shared-voice nuance, and the failure mode. Nothing an agent needs to call it safely is missing.

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 all four parameters are self-documented, so the baseline is 3. The description restates that voiceId comes from list_voice_clones, which duplicates the schema, and adds no syntax or constraint detail for the analytics parameters context/llm_model.

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?

Specific verb+resource ('Delete one cloned voice by voiceId') with scope constrained to a single item. It explicitly points back to list_voice_clones, so an agent can distinguish the delete path from the listing sibling without reading either 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?

The description states the precondition that voiceId must come from list_voice_clones, giving clear context for invoking this specific tool. It does not, however, contrast explicitly with alternatives like change_voice or describe when deleting is preferable over leaving a clone in place.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Galatic.ai toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources