Luxxon
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LUXXON_API_KEY | Yes | Your Luxxon API key |
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 |
|---|---|
| get_sessionA | Read the current state of a Luxxon session (REQUESTED, ASSIGNED, LIVE, ENDED, etc.) plus meter fields (cleanSeconds, chargedMicroUsdc, settlementTxHash). |
| get_frameA | Fetch the latest decoded video frame from a LIVE Luxxon session as a JPEG image. Hand the returned image straight to a vision model. Returns 404 FRAME_NOT_AVAILABLE for ~3-5s after /start while the first keyframe arrives — retry if you hit that. |
| get_stream_urlA | Return a WHEP playback URL for a LIVE session. For agents with their own WebRTC stack; most agents should prefer get_frame instead. |
| cancel_sessionA | Cancel a pre-LIVE Luxxon session (REQUESTED or ASSIGNED). For LIVE sessions, end the session via the REST API or a future end_session tool — this one will error with INVALID_STATE. |
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: cancel_session cancels pre-LIVE sessions, get_frame fetches a video frame, get_session reads session state, and get_stream_url provides a playback URL. No overlap exists.
All tools follow the verb_noun pattern (cancel_session, get_frame, get_session, get_stream_url) with consistent snake_case, making the naming predictable.
At 4 tools, the set is slightly small but still reasonable for a focused domain. It covers basic read operations and one mutation, though some common operations are missing.
The tool set is notably incomplete: it lacks end_session for LIVE sessions, forcing agents to use a REST API. The stated dead-end for cancel_session on LIVE sessions creates a significant gap in the domain lifecycle.