Skip to main content
Glama
Sign In
pyularn-mcp

pyularn-mcp

by R0x7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_screen

Retrieve the current 80x24 Ularn game screen without sending input, so AI agents can inspect the game state before deciding their next move.

Instructions

Return the current 80x24 game screen without sending input.

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": "get_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses two behavioral facts: the fixed 80x24 dimensions and that no input is transmitted (implying a safe read). It does not state the return format of the screen, whether the call refreshes or advances anything, or how errors are surfaced.

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 key constraint is stated early. It is efficient, though its brevity leaves information elsewhere rather than being self-sufficient.

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 zero-parameter read tool this covers the essentials (what is returned and its size, and that nothing is sent). However, with no output schema present, the description should say more about the shape of the returned screen, which is the entire payload.

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?

The tool takes zero parameters, so there is no parameter semantics to add beyond the schema; the baseline of 4 applies. The description correctly makes no parameter claims.

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?

The description states a specific verb and resource: 'Return the current 80x24 game screen.' The clause 'without sending input' implicitly separates it from send_keys and move, but it never explicitly contrasts with the sibling get_state, so an agent must infer the screen-vs-state boundary.

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?

'Without sending input' implies a passive observation call, which suggests when to use it over send_keys or move, but there is no explicit when-to-use or when-not-to-use guidance and no mention of get_state as an alternative.

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