mcp-server-return-to-dark-tower

Overview Schema Source Related Servers Discussions Admin

Send Tower State

tower_send_state

Send a complete tower state to the physical board game tower, directly setting all hardware state including lights, sound, and drum rotation.

Instructions

Send a complete tower state to the tower. Advanced: directly sets all tower hardware state.

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_send_state"
  }
}

Input Schema

Name	Required	Description	Default
`state`	No	Complete TowerState object to send to the tower

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It mentions 'directly sets all tower hardware state' implying total overwrite, but fails to disclose prerequisites (connection state), reversibility, side effects (hardware actions), or error conditions. This is insufficient for a potentially destructive hardware operation.

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

Conciseness4/5

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

Description is concise, two sentences with no wasted words. It is front-loaded with the primary action. Could be slightly more structured but efficient.

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

Completeness2/5

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

For a tool with no output schema and no annotations, the description lacks important context about return values, side effects, and preconditions. It does not mention whether a connection is needed, what happens on failure, or how the state object is validated. Incomplete for safe usage.

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

Parameters3/5

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

Schema coverage is 100% with a single 'state' parameter described. The tool description repeats the schema's description and adds 'Advanced: directly sets all tower hardware state' but does not provide format or validation details beyond what the schema offers. Baseline 3 is appropriate.

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

Purpose4/5

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

The description clearly states the action ('Send a complete tower state') and the resource (tower). The term 'Advanced: directly sets all tower hardware state' adds context, distinguishing it from higher-level state-modifying tools. However, it does not explicitly differentiate from sibling tools like tower_set_led or tower_rotate, but the broad scope is implied.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The 'Advanced' label hints at expert use, but there is no explicit when-to-use, when-not-to-use, or mention of alternatives such as individual setter tools.

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