Lotus Wisdom MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOTUS_DEBUG | No | Enable debug mode for development | false |
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 |
|---|---|
| lotuswisdomA | Contemplative reasoning tool. Use for complex problems needing multi-perspective understanding, contradictions requiring integration, or questions holding their own wisdom. Workflow: Always start with tag='begin' (returns framework). Then continue with contemplation tags. Do NOT output wisdom until status='WISDOM_READY'. Tags: begin (FIRST - receives framework), then: open/engage/express (process), examine/reflect/verify/refine/complete (meta-cognitive), recognize/transform/integrate/transcend/embody (non-dual), upaya/expedient/direct/gradual/sudden (skillful-means), meditate (pause). |
| lotuswisdom_summaryB | Get a summary of the current contemplative journey |
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 2 tools
The two tools have clearly distinct purposes: 'lotuswisdom' is for active contemplative reasoning with a structured workflow, while 'lotuswisdom_summary' is for retrieving a summary of the current journey. There is no overlap or ambiguity between them.
Both tools follow a consistent naming pattern with the 'lotuswisdom' prefix and descriptive suffixes ('lotuswisdom' and 'lotuswisdom_summary'). This creates a predictable and readable convention across the tool set.
With only two tools, the server feels under-scoped for its apparent domain of contemplative reasoning and wisdom generation. The core 'lotuswisdom' tool has a complex workflow with many tags, suggesting that additional supporting tools (e.g., for managing or querying specific aspects) would be appropriate to provide a more complete surface.
The tool set is severely incomplete for the domain. While 'lotuswisdom' handles the main reasoning process and 'lotuswisdom_summary' provides summaries, there are obvious gaps: no tools for managing or resetting contemplative sessions, querying intermediate states, or handling errors within the complex workflow. This will likely cause agent failures or dead ends.