kwctl
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KILAWATT_API_KEY | Yes | Kilawatt API key (starts with kw_live_) |
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 |
|---|---|
| deploy_gpu_nodeA | Provision real GPU compute on Kilawatt Cloud. Charges the caller's Kilawatt wallet and starts an actual machine. Set dry_run to true to price the run and check balance, spend caps, rate limits and concurrency without provisioning or charging anything. |
| x402_quoteB | Get the current price and Base USDC payment details for a GPU job without paying. |
| x402_run_jobB | Quote and, only with confirm=true and all spend caps passing, pay for one GPU job in Base USDC. |
| x402_job_statusB | Get the status of a job created through x402 using this server's locally saved API key. |
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
The x402 trio (quote/run_job/status) has a clear preview-pay-check progression, but deploy_gpu_node overlaps heavily with x402_run_job since both provision GPU compute and charge the caller, and both support a dry-run/quote mode that echoes x402_quote. An agent could reasonably misselect between the Kilawatt-wallet path and the Base USDC x402 path.
Three tools use a consistent x402_ prefix while deploy_gpu_node stands alone, and the verb/noun ordering varies across the set (x402_quote vs x402_job_status vs x402_run_job). It remains readable but the convention is not uniform.
Four tools is on the lean side but fits the narrow domain of quoting, paying for, provisioning, and checking a single GPU job. Each tool maps to a distinct step in that lifecycle with little redundancy.
The quote/pay/status/deploy lifecycle is covered, but there is no cancel, refund, list-jobs, or log/result-retrieval operation, so an agent facing a failed or stuck job has limited recourse. The two parallel execution paths (x402 vs Kilawatt) also leave ambiguous ownership of follow-up operations.