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

Calibrate Tower

tower_calibrate

Calibrates the tower drums by rotating them to their home positions after Bluetooth connection. Resets physical board game components.

Instructions

Calibrate the tower drums. Must be connected first. The tower will rotate all drums to their home positions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It states the drums rotate to home but does not disclose side effects, reversibility, or impact on other state (e.g., seals).

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 focused sentences with no fluff. Front-loaded with the main action and followed by a critical prerequisite.

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

Completeness4/5

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

Given no parameters or output schema, the description is sufficiently complete for a simple calibration action. However, more context on the calibration's purpose or effects would elevate it.

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?

There are no parameters, and schema coverage is 100%. The description adds no parameter details, but none are needed; baseline for zero parameters is 4.

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 tool calibrates tower drums by rotating them to home positions, distinguishing it from sibling rotation tools like tower_rotate 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 includes a prerequisite ('Must be connected first') but does not specify when to use this tool versus alternatives like tower_rotate or tower_random_rotate.

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