Skip to main content
Glama
Sign In
m8-tracker-mcp

m8-tracker-mcp

by cocopon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get M8 screen text

get_screen

Reads the current Dirtywave M8 screen as text with inline color tags, palette mappings, and cursor position/text for remote inspection.

Instructions

Returns the current M8 screen as text with inline color tags. A Palette section maps slot letters to fg/bg colors. In the Screen section, "{x}" switches the color to slot x until the next tag; each line starts in slot "a". Spaces do not trigger tags. The Cursor section gives the line (1-based within the Screen section), the columns (1-based, not counting {x} tags) and the text inside the cursor frame.

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

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it explains the Palette mapping, the inline {x} color-tag semantics, per-line slot-a reset, and the 1-based indexing of the Cursor section. It stops short of stating that the call is side-effect-free, what happens when the device is not connected, or any error behavior.

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?

Front-loads the return-summary sentence before the Palette/Screen/Cursor breakdown, and every sentence (including the 'spaces do not trigger tags' edge case) adds usable parsing detail. Slightly dense but no filler.

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?

Because there is no output schema, the description must decode the returned text, and it does so thoroughly enough for an agent to parse colors and cursor position. The only missing piece is a note on connection state or failure mode.

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 nothing for the description to disambiguate; baseline is 4 and no parameter-related gaps exist.

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?

States a specific verb and resource ('Returns the current M8 screen as text') plus the format it comes in, which an agent can distinguish instantly from the neighboring press_*/connect/disconnect tools.

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?

Usage is only implied by the read-style verb; there is no explicit statement of when to call this versus press_sequence or get_system_info, and no mention of preconditions such as requiring an active connection.

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