Skip to main content
Glama
Sign In
@omnidim-ai/mcp-server

@omnidim-ai/mcp-server

by Omnidim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getClonedVoice

Read-only

Retrieve a cloned voice by ID to view its details and creation status.

Instructions

One cloned voice, including its creation status. (Tags: Voice cloning)

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": {
      "voice_id": "<voice_id>"
    },
    "name": "getClonedVoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
voice_idYesId of the cloned voice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.14.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false so the safety profile is covered. The description adds that the response includes creation status, a useful behavioral detail, but nothing about errors for invalid/missing voice_id.

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?

A single compact sentence, front-loaded with the resource and disclosing the key returned field. Zero waste.

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 simple one-param read tool with annotations and a fully-described schema and no output schema, the definition is nearly complete. Only minor gap is not stating behavior on unknown voice_id or that status values are enumerated.

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?

Single required param with 100% schema coverage; the schema describes voice_id fully. The description adds nothing beyond 'a cloned voice' which the schema already conveys, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: retrieves a single cloned voice, and calls out the creation status. It contrasts implicitly with listClonedVoices and sibling getVoice, though it doesn't explicitly differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the singular 'one cloned voice' versus the plural listClonedVoices sibling, but there is no explicit when-to-use or when-not-to-use guidance.

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

Deploy Server

Other Tools