GenieLocker — Private AI by the Minute
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| genie_statusA | Read current catalog, capacity, sellability, locker counts, and payment-rail status. This never creates or purchases a locker. |
| genie_catalogA | Read only the lifecycle-verified SKUs that are currently eligible for purchase. Designed or benchmarked recipes are not represented as commercial inventory. |
| genie_quoteA | Get a live, non-binding price quote. This is read-only and does not reserve capacity, create an account, or spend funds. |
| genie_recipesA | Search the public recipe menu by maturity, category, or text. The stage field is authoritative: only stage=commercial is live inventory. |
| genie_credit_pricingA | Read the current credit definition, burn multipliers, tier pricing, and examples. This never creates a wallet or buys credits. |
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 5 tools
Each tool targets a distinct aspect: overall status, purchasable catalog, quotes, recipes, and credit pricing. The descriptions clearly differentiate catalog (commercial-only) from recipes (all stages), eliminating ambiguity.
All tools follow the consistent 'genie_' prefix followed by a descriptive noun (status, catalog, quote, recipes, credit_pricing). This uniform pattern is predictable and easy to navigate.
Five tools is an ideal size for a read-only information server, covering the essential domain areas without unnecessary bloat or sparsity.
The surface comprehensively covers the informational needs of the domain: overall status, available inventory, live pricing, recipe search, and credit definitions. Since all tools are explicitly read-only, there are no missing write operations for this server's stated purpose.