Skip to main content
Glama
Sign In
pyularn-mcp

pyularn-mcp

by R0x7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

move

Directs the player one or more steps in a compass direction, or runs until something interesting occurs, for AI-agent navigation in Ularn.

Instructions

Move the player one or more steps in a compass direction (or run until something interesting).

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": {
      "direction": "<direction>"
    },
    "name": "move"
  }
}

Input Schema

NameRequiredDescriptionDefault
runNoRun in that direction instead of stepping.
countNoNumber of steps (default 1).
directionYes
include_stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It hints at run behavior ('until something interesting') but never says whether movement can be blocked, whether it consumes turns, what happens on invalid directions, or whether include_state changes the response, leaving key behavior undisclosed for a state-mutating tool.

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?

A single front-loaded sentence with no filler. The closing parenthetical is compact but slightly vague in wording ('something interesting').

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 4-parameter, state-changing game tool with no annotations and no output schema, the definition omits what include_state returns, what the run stop condition actually is, and how blocked or invalid moves are reported. The core action is covered but material gaps remain.

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?

The description reinforces count ('one or more steps') and run ('until something interesting'), but those are already described in the schema, and include_state is undocumented in both schema and description. At 50% coverage the description only marginally compensates.

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?

States a specific verb ('Move') and target ('the player') plus the axis of movement (compass direction), which is clear. It does not explicitly distinguish itself from send_keys, which could also produce movement, so sibling differentiation is implicit rather than stated.

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 parenthetical 'or run until something interesting' implies when to use the run variant, but there is no explicit guidance on when to choose move over send_keys or get_state, and no stated preconditions or failure cases.

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