Skip to main content
Glama
Sign In
mcp-server-return-to-dark-tower

mcp-server-return-to-dark-tower

by ChessMess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

All Lights On

tower_lights_on

Activate all 24 tower LEDs with a single command. Optionally choose an effect: on, breathe, or flicker.

Instructions

Turn on all 24 tower LEDs with a single command. Optionally specify an effect (0=off, 1=on, 2=breathe, 3=breatheFast, 4=breathe50%, 5=flicker); defaults to on.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tower_lights_on"
  }
}

Input Schema

NameRequiredDescriptionDefault
effectNoEffect to apply to all LEDs (default: 1=on)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It clearly states action (turn on all LEDs) and effect parameter options. No destructive behavior or hidden traits mentioned, but for a simple command it is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: first declares purpose, second explains parameter. No redundant information. Front-loaded with action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given single parameter, no output schema, and straightforward action, the description covers all necessary information. Sibling tools are numerous but description specifies scope (all LEDs) clearly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description for effect is minimal ('Effect to apply to all LEDs'), but tool description enumerates all mappings (0=off, 1=on, etc.), adding significant meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool name and title clearly indicate turning on all lights. Description specifies 'all 24 tower LEDs' and distinguishes from siblings like tower_set_lights (individual control) and tower_lights_off.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description states 'with a single command' implying simplicity, and optionally specifies effect parameter. However, it does not explicitly contrast with alternatives (e.g., tower_set_lights for individual LEDs) or provide when-not scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools