Skip to main content
Glama
jtannahill

amaran-mcp

by jtannahill

Related Servers

Alternatives to amaran-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a distinct verb targeting a different aspect of the lamp's state (power, brightness, white, colour, effect, scene, music mode), and descriptions explicitly clarify boundaries, e.g. set_brightness noting it only adjusts brightness while preserving the current mode. The only mild conceptual overlap, start_music_mode vs set_effect, is resolved by describing music mode as a separate behaviour. An agent can pick the right tool from names alone.

    Naming Consistency5/5

    All twelve tools follow a strict snake_case verb_noun pattern (get_light, set_power, stop_effect, save_scene, start_music_mode), with natural mirrored pairs like start_music_mode/stop_music_mode and save_scene/recall_scene. No mixed casing or inconsistent verb styles.

    Tool Count5/5

    Twelve tools is well within the ideal 3-15 range for a single-device lighting controller. Every tool maps to a real capability (state read, each light attribute, effects, scenes, music mode) without redundant entries.

    Completeness4/5

    The surface covers the full lifecycle for light control: read state, set power/brightness/colour/white, start and stop effects, save and recall scenes, and music mode. The main gap is scene management beyond save/recall — there is no delete_scene or rename, so saved scenes can only be overwritten, not removed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues