Skip to main content
Glama

Get MiSTer status

mister_get_status
Read-only

Inspect status for one or all configured MiSTer FPGA devices to find reachable hosts, active cores, current game, capabilities, limitations, and attract-mode state.

Instructions

<use_case> Inspect status across all configured MiSTer FPGA devices or a single target device. </use_case> <important_notes>

  • Start here: lists reachable devices, active cores, currently playing game ref, and capabilities/limitations.

  • limitations flags missing Zaparoo Core or unconfigured SSH.

  • attract_mode indicates active MiSTer Super Attract Mode demo cycle. </important_notes>

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

Input Schema

NameRequiredDescriptionDefault
hostNoMiSTer name from mister_get_status. Omit when the call already says which (a ref does).

Output Schema

NameRequiredDescriptionDefault
hostsYes
dry_runYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: what the response surfaces (reachable devices, active cores, playing game ref, capabilities/limitations), what the limitations flag means (missing Zaparoo Core or unconfigured SSH), and what attract_mode indicates. These are useful return-value semantics, though much overlaps with the existing output schema.

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?

The use_case and important_notes sections are well structured and front-loaded, with the entry-point guidance first. Slight overlap between the bullet describing return contents and the existing output schema means not every line adds unique value.

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?

For a zero-required-parameter read tool with annotations and an output schema, the description supplies the missing orientation: what the call is for, what it returns at a high level, and how to interpret the limitations and attract_mode flags. Little is left ambiguous for correct invocation.

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?

There is a single optional host parameter with full schema description coverage that already explains it is a MiSTer name and can be omitted when a ref identifies the device. The description adds no syntax, format, or selection detail beyond the schema, so the baseline 3 applies.

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 ('Inspect status across all configured MiSTer FPGA devices or a single target device') and scopes the result to per-device or aggregate. It positions itself as the entry point ('Start here') but does not explicitly distinguish itself from siblings such as mister_list_systems or mister_get_ini, leaving some differentiation implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Start here' gives clear when-to-use guidance as the discovery first step, and the host parameter note ('Omit when the call already says which (a ref does)') tells the agent when the parameter can be skipped. It stops short of explicit when-not or named alternatives, so a 4 rather than 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.