Skip to main content
Glama
Sign In
voicesmith

voicesmith

by fergo5002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Voice Info

voice_info

Retrieve details for a specific cloned voice, including references, statistics, and tuning parameters.

Instructions

Details for one voice: references, stats and tuning.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must carry the behavioral burden, but it does not state that this is a read-only lookup, what happens for an unknown voice name, or whether any auth is required. Only 'Details' hints at a non-mutating operation.

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

Conciseness3/5

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

It is a single short sentence with no waste and is front-loaded, but the terseness comes at the cost of substance rather than reflecting genuine efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, which lightens the burden considerably. Still, the undocumented 'name' parameter and absent behavioral notes leave meaningful gaps for an agent to guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter 'name' has 0% schema description coverage, and the description does not clarify whether it is a voice ID, display name, or slug, nor any format constraints. 'one voice' is the only link between the parameter and its meaning.

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

Purpose3/5

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

The description identifies the resource (a single voice) and the kind of content returned (references, stats, tuning), which implicitly contrasts with the plural list_voices sibling. However, 'references' and 'tuning' are jargon whose meaning an agent cannot infer, and there is no clear verb such as 'retrieve' or 'get'.

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

Usage Guidelines2/5

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

There is no statement of when to call this tool versus list_voices or any other sibling, and no prerequisites or exclusions. The phrase 'one voice' only weakly implies a single-entity lookup.

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