windy-word-mcp

set_active_voice_clone

Select a voice clone for text-to-speech output, or deactivate to revert to built-in TTS.

Instructions

Set which voice clone is the active TTS default. Pass id=null to deactivate (no clone — falls back to built-in TTS). The id must match an existing clone (use list_voice_clones to discover ids).

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Clone id, or null to deactivate.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.11.0Jul 29, 2026

TDQS

A4.7/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that setting a clone activates it as default TTS, deactivation falls back to built-in TTS, and id must match existing clone. Could mention persistence or error behavior but covers key traits.

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?

Two sentences, extremely concise, no redundant information. Purpose is front-loaded, and every sentence adds necessary context.

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?

Given one parameter and no output schema, the description covers the core scenario and deactivation. Referencing the discovery tool adds completeness. Could include return value info, but sufficient for a setter tool.

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

Parameters5/5

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

Schema covers 100% of parameters with description 'Clone id, or null to deactivate.' Description adds value by explaining null behavior and the prerequisite of an existing clone, referencing a sibling tool.

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?

Description clearly states 'Set which voice clone is the active TTS default', specifying verb (set) and resource (active voice clone). It distinguishes from siblings like get_active_voice_clone (read) and list_voice_clones (list) by focusing on setting and deactivation.

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 says when to pass null to deactivate, and instructs to use list_voice_clones to discover ids. This provides clear context and an alternative tool for discovery.

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

Deploy Server