MasterMind Lite
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mastermind_exactA | Send exactly the supplied prompt, unchanged, to Claude, Gemini, and Grok independently. Use this when the user says 'same prompt', 'exact prompt', 'exactly this', or equivalent. Do not rewrite, summarize, prepend, append, or provider-specialize prompt. On the first MasterMind call, create a short stable topic-based thread_key; reuse it on later calls in this chat unless the user asks for a fresh/reset thread. Do not ask the user to invent a key unless necessary. The result echoes thread_key and a SHA-256 hash. Defaults are used automatically. Only when the user explicitly requests a different setting, pass provider_overrides, for example {'claude': {'preset': 'Opus 5 / High'}} or {'grok': {'preset': 'Simple'}}. A custom override may instead contain model and/or effort. Overrides are metadata and must never be inserted into the prompt. Changing resolved model or effort restarts only that provider's native session. |
| mastermind_feedbackA | Send one self-contained briefing, unchanged, to Claude, Gemini, and Grok independently. Before calling, read relevant current conversation context and write a neutral briefing that includes the complete prompt/artifact/plan being reviewed, decisions already made, and the exact question. Include only context that helps. Do not anchor advisers with one another's responses unless the user explicitly asks. The service does not construct or edit the briefing. Create a short stable topic-based thread_key on the first call and reuse it later in this chat. Defaults are used automatically. Only when the user explicitly requests a different setting, pass provider_overrides, for example {'claude': {'preset': 'Opus 5 / High'}} or {'grok': {'preset': 'Simple'}}. A custom override may instead contain model and/or effort. Overrides are metadata and must never be inserted into the prompt. Changing resolved model or effort restarts only that provider's native session. |
| mastermind_reset_threadA | Forget the local Claude, Gemini, and Grok session mappings for thread_key. Use when the user asks to start fresh; a later consultation creates three new native conversations. |
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
reset_thread is clearly distinct, but exact and feedback both fan out unchanged content to the same three providers, so their boundary depends on intended usage rather than different mechanics. The descriptions provide useful cues, so misselection is possible but not severe.
All names share the mastermind_ prefix and snake_case, which is readable. However, only reset_thread follows a verb_noun pattern; exact and feedback are noun/adjective labels, making the overall convention mixed.
Three tools form a minimal but focused surface for a Lite multi-model consultation server. Each tool has a role, though the set is slightly thin for full thread lifecycle management.
Core operations are covered: send exact prompts, send briefing-style feedback, and reset thread mappings. Minor gaps exist, such as no way to list or inspect existing thread_key mappings, but agents can work around this.