Mnemonica Strategy
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| executeC | Execute a command in the specified context (MCP, RPC, or RUN) |
| listB | List all available commands grouped by context and folder |
| helpB | Get detailed help for a specific command including examples |
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 clearly distinct purpose: execute performs actions, help provides documentation, and list enumerates available commands. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent, simple verb-only pattern (execute, help, list). This uniformity makes the set predictable and easy to understand, with no deviations in naming style.
With only 3 tools, the set feels thin for a strategy server, potentially lacking depth in operational coverage. While the tools are well-defined, the low count may limit the server's utility in complex scenarios, though it's not extreme.
The tool surface is significantly incomplete for a strategy domain; it only covers command execution, help, and listing, with no tools for planning, analysis, or decision-making. This creates obvious gaps that could lead to agent failures in strategic tasks.