sinum-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SINUM_API_KEY | Yes | Your API key for the Sinum system | |
| SINUM_API_URL | No | Sinum API URL | http://sinum.local/api/v1 |
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 |
|---|---|
| device_listB | Retrieves a list of all devices/features in the Sinum smarthome system |
| scene_listA | Retrieves a list of all scenes in the Sinum smarthome system |
| scene_activateB | Activates a scene with the given ID in the Sinum smarthome system |
| toggle_lightA | Toggles the state of a light (on/off) for devices of type relay with purpose === light |
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 targets a distinct functionality: device listing, scene listing, scene activation, and light toggling. There is no overlap or ambiguity.
Tools use snake_case, but patterns vary: two use 'noun_list' (device_list, scene_list) and two use 'verb_noun' (scene_activate, toggle_light). Mostly consistent with minor deviation.
Four tools is a reasonable number for a basic smarthome server. It covers core operations without being too sparse or overloaded.
The set covers essential device listing, scene management, and light toggling, but lacks control over other device types (e.g., temperature, blinds) and advanced operations like brightness or scene creation, leaving notable gaps.