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

Random Rotate

tower_random_rotate

Randomly rotate selected drum levels on the Return to Dark Tower game tower. Choose which levels to spin: all, top, middle, bottom, or combinations.

Instructions

Randomly rotate drum levels. level: 0=all, 1=top, 2=middle, 3=bottom, 4=top+middle, 5=top+bottom, 6=middle+bottom

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

Input Schema

NameRequiredDescriptionDefault
levelNoWhich drums to rotate randomly (0=all, default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose side effects, such as whether the rotation is destructive, requires specific conditions, or affects other state. The random nature is mentioned but not elaborated.

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 concise sentences: one for purpose, one for parameter details. No wasted words.

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?

For a simple one-parameter tool with no output schema, the parameter mapping is well covered, but missing details on the exact behavior of 'randomly rotate' (e.g., how many rotations, direction, timing). Adequate but not fully complete.

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

Parameters4/5

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

Schema coverage is 100% (single parameter 'level'), and the description adds detailed meaning by explaining each value (0=all, 1=top, etc.), going beyond the basic schema description.

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 the action ('Randomly rotate drum levels') and explains the parameter mappings, distinguishing it from sibling tools like tower_rotate (specific rotation) and tower_rotate_drum (single drum).

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 (e.g., tower_rotate, tower_rotate_drum) or any prerequisites. The description only states what it does, not when to choose it.

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