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

Rotate All Drums

tower_rotate

Rotate top, middle, and bottom drums of the Return to Dark Tower game to specified compass directions; optionally play a sound during rotation.

Instructions

Rotate all three drums to specified positions. Requires calibration. Optionally plays a sound.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "top": "<top>",
      "middle": "<middle>",
      "bottom": "<bottom>"
    },
    "name": "tower_rotate"
  }
}

Input Schema

NameRequiredDescriptionDefault
topYesTarget position for top drum
bottomYesTarget position for bottom drum
middleYesTarget position for middle drum
soundIndexNoOptional sound to play during rotation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It lacks details on side effects, what happens if calibration is missing, or whether the rotation is instantaneous or queued.

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?

The description is a single concise sentence that front-loads the main action. It could benefit from better structure (e.g., prerequisites), but it is efficient.

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

Completeness3/5

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

Given no output schema, the description does not explain return values. It mentions calibration but lacks error conditions or state change details. Adequate for a simple tool.

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%, but the description only adds 'Optionally plays a sound' for soundIndex. For the required parameters, it adds minimal value 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?

The description clearly states 'Rotate all three drums to specified positions', using a specific verb and resource. It distinguishes this from sibling tools like tower_rotate_drum (single drum) and tower_random_rotate.

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

Usage Guidelines3/5

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

The description mentions 'Requires calibration' as a prerequisite, but does not explicitly state when to use or alternatives compared to other rotate tools.

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