Rime MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RIME_VOICE | No | The default voice to use (default: "cove") | |
| RIME_API_KEY | Yes | Your Rime API key from the Rime Dashboard | |
| RIME_GUIDANCE | No | The main description of when and how to use the speak tool | |
| RIME_WHEN_TO_SPEAK | No | When the tool should be used (default: "when asked to speak or when finishing a command") | |
| RIME_WHO_TO_ADDRESS | No | Who the speech should address (default: "user") |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| speakA | Speak text aloud using Rime's text-to-speech API. Should be used when user asks you to speak or to announce and explain when you finish a command User configuration: WHO_TO_ADDRESS: user WHEN_TO_SPEAK: when asked to speak or when finishing a command VOICE: cove GUIDANCE: Use the speak tool to convert text to speech when the user requests audio output or when providing verbal responses |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The speak tool has a single, clearly defined purpose for text-to-speech conversion.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'speak' follows a clear verb pattern appropriate for its function.
A single tool is too few for most MCP server purposes, even for a text-to-speech service. This feels thin and limited, lacking complementary tools like volume control, voice selection, or speech status checks that would enhance functionality.
The tool surface is severely incomplete for a text-to-speech domain. While the speak tool covers the core output function, there are obvious gaps such as no tools for managing voices, adjusting speech parameters, stopping speech, or checking speech status, which limits agent capabilities.