Quantum Agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_API_KEY | No | API key for Groq provider | |
| GEMINI_API_KEY | No | API key for Google Gemini provider | |
| OPENAI_API_KEY | No | API key for OpenAI provider | |
| DEEPSEEK_API_KEY | No | API key for DeepSeek provider | |
| ANTHROPIC_API_KEY | No | API key for Anthropic Claude provider |
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 |
|---|---|
| quantum_init_taskC | HOST AI CONTROL: Initializes a quantum superposition task directly for the connected AI (Gemini, Claude, ChatGPT). Generates orthogonal basis states without requiring external API keys. |
| quantum_stepC | HOST AI CONTROL: The connected AI directly submits its evaluation for a quantum branch. Quantum Agent applies Grover amplitude amplification or destructive pruning, tests convergence, and returns the next priority branches. |
| quantum_system_infoB | Displays Quantum Agent operating mode (Host AI direct control vs Standalone Terminal mode) and active system parameters. |
| quantum_solveB | Autonomous solver: Solves complex coding, research, or diagnostic problems using superposition search and exact convergence verification. |
| quantum_explore_branchesD | Decomposes any complex problem into orthogonal quantum basis states (multi-dimensional parallel hypotheses). |
| quantum_tunnelC | Forces an out-of-the-box lateral quantum tunnel leap to escape local reasoning traps or defensive bottlenecks. |
| quantum_session_statusB | Queries persistent status, continuous uptime, evaluated possibilities, and convergence state for a Quantum Agent session. |
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 7 tools
quantum_init_task and quantum_explore_branches both claim to decompose a problem into orthogonal basis states, differing only by a 'host AI control' nuance, and quantum_solve vs. quantum_step (autonomous vs. host-driven evaluation) overlaps heavily. quantum_tunnel and quantum_system_info are distinct, but the core workflow tools have unclear boundaries that will cause misselection.
All tools use a uniform snake_case quantum_ prefix, which is highly predictable. The only minor deviation is mixing verb-style (step, solve, tunnel, init_task) with noun-style (session_status, system_info) suffixes, which is still readable.
Seven tools is a well-scoped size for a quantum-search workflow covering init, explore, step, solve, status, info, and tunnel. The count would be ideal if the near-duplicate init/explore pair were consolidated.
The set covers initialization, exploration, iteration, solving, and status inspection, but has no session termination/reset, no session listing, and no explicit result/answer retrieval endpoint — only status queries. These gaps force agents to leave sessions dangling and infer outcomes from status.