Skip to main content
Glama
ollama-tts-mcp

ollama-tts-mcp

stop_speaking

Stops current text-to-speech playback and clears any queued audio, so spoken output ends immediately.

Instructions

Stop the speech that is playing now and drop anything queued after it.

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": "stop_speaking"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the important side effect that queued utterances are discarded, not resumed, which is real behavioral value beyond the schema; however, it says nothing about the no-op case (idle state), whether the stop is immediate or at an utterance boundary, or whether any confirmation/error is raised.

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 sentence with the action front-loaded and the queue-clearing consequence attached immediately after. Every clause adds information; nothing is redundant or padded.

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 zero-parameter playback control with an output schema available, the description covers the action and its main consequence adequately. The remaining gap is idle-state behavior, which is minor but would be useful for an agent deciding whether the call is safe to issue unconditionally.

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, so there is nothing for the description to disambiguate and the baseline of 4 applies. The sentence correctly implies a parameterless call by referring only to implicit current playback state.

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?

States a specific verb ('Stop') against a specific resource ('the speech that is playing now') and adds the scope of clearing the queue. It is immediately distinguishable from the siblings speak/text_to_speech, which start playback rather than end it.

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 'call this to halt playback,' and the sibling set makes the alternative (continue speaking) obvious. There is no explicit when-to-use/when-not guidance, no statement about calling it when nothing is playing, and no named alternative.

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