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

Get Glyph Position

tower_get_glyph

Look up the current facing direction of a specific glyph, such as cleanse or battle, to determine its status in the board game.

Instructions

Get the current facing direction of a specific glyph

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": {
      "glyph": "<glyph>"
    },
    "name": "tower_get_glyph"
  }
}

Input Schema

NameRequiredDescriptionDefault
glyphYesThe glyph to look up

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 are provided, so the description carries the full burden. It states 'current facing direction' but does not specify the format (e.g., degrees, compass direction), behavior on invalid input, or whether it returns a scalar or object. This lack of detail impairs safe invocation.

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?

The description is a single concise sentence with no filler. Every word contributes to the purpose.

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 lookup with one parameter, the description is minimally adequate. However, it omits the output format (e.g., numeric angle, cardinal direction) and edge cases, which a complete description would include. Given the absence of output schema, more details would be helpful.

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%, so the baseline is 3. The description adds no additional meaning beyond 'specific glyph'. It does not explain what each glyph value represents or how the direction is returned relative to the parameter.

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 uses a specific verb 'Get' and resource 'facing direction of a specific glyph', clearly distinguishing it from sibling tools like `tower_get_glyphs` and `tower_glyphs_facing`, which likely handle multiple glyphs or general facing info.

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?

No explicit guidance on when to use this tool over siblings or when not to use it. The context is implied (for a single glyph's facing direction), but neither alternatives nor exclusions are mentioned.

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