TrueVoice MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_human_writing_rulesA | Get comprehensive rules for writing like a human and avoiding AI slop. Use these rules as system-level instructions for any text generation task. |
| check_for_slopA | Analyze text for AI slop indicators across three categories: Information Utility, Style Quality, and Structure. Returns specific patterns to avoid. |
| get_slop_examplesB | Get examples of common AI slop phrases and patterns to avoid, categorized by type. |
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 3 tools
Each tool has a distinct purpose: retrieving rules, analyzing text for slop, and providing examples. There is no meaningful overlap between them, and their descriptions clearly separate the reference/instructional functions from the analysis function.
Tool names follow a clear and predictable lowercase snake_case pattern, mostly using get_ for reference tools and check_for_ for the analysis tool. Minor inconsistency exists between get_ and check_for_ as verb styles, but the naming remains readable and consistent overall.
Three tools is a well-scoped count for a focused MCP server centered on human writing rules and AI slop detection. Each tool serves a distinct and necessary role without bloat or redundancy.
The tool surface covers the core domain well: users can learn the rules, see examples, and check their text for slop. A minor gap is the absence of a rewrite/improvement tool, but this is not a significant failure for the apparent advisory/analysis purpose.