Skip to main content
Glama
Sign In
anki-mcp-server

anki-mcp-server

by MeisamHakimi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Text-to-speech status

anki_tts_status
Read-only

Lists available text-to-speech engines, including built-in Google voices with language codes and, if installed, AwesomeTTS presets or last used voice, to check TTS options before generating audio.

Instructions

Which text-to-speech engines are available: built-in Google voices (with language codes) and, if the AwesomeTTS add-on + bridge are installed, its presets and last used voice (never options or API keys).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint and openWorldHint already declare this as a safe local read, so the description's job is lighter. It still adds real value by disclosing that results are conditional on the AwesomeTTS add-on plus bridge being installed and that options/API keys are never returned, which tells the agent the output is safe to surface. It does not describe result shape, but an output schema exists to cover that.

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

Conciseness4/5

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

A single compact sentence with the core answer front-loaded (which engines are available) and the conditional AwesomeTTS detail trailing. The nested parentheticals add mild density but every clause carries information, notably the never-returned options/API keys caveat.

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?

The tool is a parameter-free status read with an output schema, so the description need not explain return values, and it correctly covers the two data sources and their installation precondition. The one remaining gap is a lack of explicit guidance on acting on the result, which is minor for an introspection call.

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 no parameter meaning to convey and the baseline is a 4. The schema coverage is 100% on an empty object, leaving nothing for the description to compensate for.

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?

It states precisely what the tool reports: available TTS engines, encompassing built-in Google voices with language codes plus AwesomeTTS presets and last-used voice when the add-on and bridge are present. That is far more specific than the title alone and implicitly distinguishes it from the generation sibling anki_generate_audio. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiating.

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 this is a discovery/introspection call to run before generating audio, but the description never says when to call it or what to do with the results. The conditional about AwesomeTTS hints at when extra data appears, yet no alternative tool or precondition is named.

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