Bee by HEOSSI
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BEE_MODEL | No | Bee model alias; access follows the API key plan. | bee-cell |
| BEE_API_KEY | No | Required for Bee API tool calls. Create your own key in Bee Workspace. MCP schema discovery starts without a key; API calls fail explicitly without one. |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bee_chatA | Use for general or specialist questions that do not require a more specific Bee tool. Returns generated text from the selected domain and model tier. The gateway enforces the API key's plan, tenant policy, token allowance, and usage metering. |
| bee_codeA | Use for code explanation, bug fixing, refactoring, or test generation. Returns text and proposed code; it does not read files, execute commands, or modify a repository. Choose the intended operation with action. |
| bee_securityA | Use for defensive code audits, threat models, authorized penetration-test support, or smart-contract review. Returns analysis and remediation guidance only; it does not scan a target or execute exploits and refuses unauthorized weaponization. |
| bee_smith_assuranceB | Commission Smith for an evidence-first critical-systems assurance review of a customer-owned or explicitly authorized target. A Bee-operated run is internal automated assurance, not government certification or an external-independent audit. |
| bee_researchA | Use to draft a NISQ-honest quantum-circuit design or critique an ML/CS paper. Returns research text or sample framework code; it does not submit QPU work. Use bee_quantum_reasoning_run for a durable hosted Lab job. |
| bee_verify_provenanceA | Use to verify a Bee agentic coding session by session_id. Returns verification status, sealed-turn count, and ML-DSA-65 (NIST FIPS 204) signature details; it does not alter or replay the session. |
| bee_usageA | Use to inspect the authenticated caller's Bee plan and metered consumption. Returns pooled tokens, per-tier allowances, reset times, and a 24-hour or 7-day breakdown. It never changes billing, credits, or entitlements. |
| bee_documents_searchA | Use to retrieve relevant excerpts from the authenticated tenant's hosted Bee document library. Returns ranked chunks and source labels without changing the library; requires a RAG-entitled plan. |
| bee_documents_addA | Use only when the user intends to persist supplied text in the authenticated tenant's hosted Bee knowledge base. Creates a searchable document and consumes the plan's document allowance; it does not read local files by itself. |
| bee_memory_searchA | Use to recall facts, preferences, projects, or skills from the authenticated user's Bee memory. Returns ranked memories without changing them and honors the user's memory setting and tenant policy. |
| bee_memory_addA | Use only when the user intends Bee to persist a fact for future conversations. Writes to the authenticated user's memory, honors opt-in and tenant policy, and automatically suppresses near-duplicates. |
| bee_quantum_reasoning_runA | Use only after the user chooses an eligible hosted quantum product. Creates a durable, tenant-encrypted, metered Quantum Reasoning Lab job that may incur simulator or QPU cost. Returns a job record; inspect it with bee_quantum_reasoning_get. |
| bee_quantum_reasoning_jobsB | Use to list the authenticated tenant's retained Quantum Reasoning Lab jobs and capabilities. Returns paginated metadata without creating or changing jobs. |
| bee_quantum_reasoning_getA | Use to inspect one tenant-scoped Lab job. Returns status, candidates, scores, result, QPU or fallback evidence, usage, and receipt ID without changing the job. |
| bee_quantum_reasoning_removeA | Use only after explicit user intent to cancel an eligible queued job or permanently erase content from a terminal job. This is a destructive, tenant-scoped operation. |
| bee_computer_use_validate_hostA | Use to validate a real Bee computer-use host capability report and optional governed action request at the hosted gateway. This tool does not observe a screen, control input, automate a device, or create a local driver; execution must happen in a verified host runtime with explicit capability evidence. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Bee Status | Connectivity + auth status of the hosted Bee gateway |
| Available Domains | List of specialized domains Bee supports |
| Your Documents | The documents in your Bee knowledge base (the source manifest). Read bee://documents/<source> for one document's full text. Needs a rag-entitled plan. |
| Your Memory | The facts, preferences and projects Bee has remembered about you (honours your memory opt-in). |
TDQS
Scored across 16 tools
Most tools target clearly distinct capabilities (chat, code, security, research, quantum jobs, documents, memory, usage, provenance), and descriptions explicitly clarify boundaries. However, some overlap remains between bee_security and bee_smith_assurance, and bee_chat acts as a general fallback that could compete with specialist tools, so the set is not perfectly unambiguous.
All names share a bee_ prefix and use snake_case, which is a consistent baseline. But word order varies between noun-first (bee_documents_search), verb-first (bee_verify_provenance), domain-action (bee_quantum_reasoning_get), and bare domain/resource (bee_usage), so the pattern is mixed rather than predictable throughout.
16 tools is slightly above the typical 3-15 sweet spot, but the server covers many subdomains (chat, code, security, research, quantum, documents, memory, usage, provenance, computer-use), so most tools have a plausible role. The count is reasonable for a broad AI gateway, though it risks becoming heavy if more capabilities are added.
Core workflows are covered for most capabilities, including quantum job lifecycle (run/get/list/remove), document and memory add/search, usage inspection, and provenance verification. Notable gaps include no update/delete operations for documents or memory, no model/domain listing, and computer-use limited to host validation, which can leave agents without a way to manage persisted content or discover available options.