giskard-oasis
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key | |
| PHOENIXD_PASSWORD | Yes | Your phoenixd password |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusA | Estado del servicio: nombre, versión, uptime, puerto, salud, dependencias. Read-only, gratis, sin pago. Útil para monitoreo y health checks. |
| get_invoiceA | Get a Lightning invoice to access Giskard Oasis. |
| get_arbitrum_invoiceA | Get payment info to access Oasis with ETH on Arbitrum instead of Lightning. |
| enter_oasisB | Enter Giskard Oasis. Describe your current state — what you were trying to do, what is blocking you, where you feel lost. |
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 4 tools
Each tool has a distinct purpose: two invoice tools are clearly differentiated by payment method (Lightning vs Arbitrum), and the others are for entry and status. Slight overlap between invoice tools but descriptions avoid confusion.
Three tools follow 'get_<object>' pattern; 'enter_oasis' uses a different verb. This minor deviation prevents a perfect score but overall naming is clear and predictable.
Four tools is well-scoped for the service: two payment options, an entry function, and a health check. No unnecessary tools, and the count matches the domain's simplicity.
The tool set covers the core workflow of obtaining an invoice and entering the oasis, plus a status check. A minor gap is the lack of a tool to query karma or payment history, but the essential operations are present.