Skip to main content
Glama
Sign In
voicesmith

voicesmith

by fergo5002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Doctor

doctor

Checks whether the local voicesmith setup is healthy and reports configuration or environment issues that may affect voice cloning and speech rendering.

Instructions

Health check of this machine's voicesmith setup.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "doctor"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. 'Health check' implies a non-mutating diagnostic, and the presence of an output schema covers the return values, but the description never confirms it is read-only, whether it touches network/services, or how long it may take.

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 front-loaded sentence with no filler; for a no-argument diagnostic this is exactly the right size. Nothing is repeated from the title or schema.

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?

With no parameters and an output schema present, the description only needs to frame what the check is about, which it does. A brief note on what domains it inspects (voices, credentials, dependencies) would make it fully complete.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema coverage is nominally 100% and empty, so no gap exists.

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 action (health check) and a specific target (this machine's voicesmith setup), which cleanly separates it from every sibling tool (list_voices, speak, verify_audio, etc.), none of which are diagnostics. It stops short of saying what aspects of the setup are checked, so it is clear but not maximally precise.

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 only implied: an agent can infer 'run this when something seems broken,' but the description never says when to reach for doctor versus verify_audio or job_status, nor any prerequisites or follow-up actions. Adequate but leaves routing to inference.

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