Wuniq
OfficialServer 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 |
|---|---|
| runA | Run a Wuniq Knowledge Engine command to discover projects or read and maintain local .wuniq knowledge. Use it for open, read, search, graph, new, edit, relation, sync, or help; use native tools for ordinary project files. Supply one shell-like string: start with open list and use help for exact syntax. Read commands do not mutate; writes may create, update, move, or delete .wuniq context, and sync reconciles it. Returns plain text. Local-only: no account, remote authentication, or rate limit. Requires the free desktop app; otherwise returns installation guidance. |
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
The single 'run' tool is overloaded with many distinct commands (open, read, search, graph, new, edit, relation, sync, help), making it ambiguous what it does and when to use it versus native tools. Agents may struggle to determine the correct command or differentiate from other tools.
With only one tool named 'run', there is no pattern to evaluate. The name is overly generic and does not reflect any domain-specific convention.
A single tool for a knowledge engine that supports multiple diverse operations is far too few. Typically, such a domain would require separate tools for each operation (e.g., search, read, create) to avoid overloading and improve clarity.
While the tool claims to cover many actions, it is monolithic and may be incomplete for complex workflows. The description also defers 'ordinary project files' to native tools, creating potential gaps and reliance on external tools.