Skip to main content
Glama

List systems

mister_list_systems
Read-only

Lists indexed gaming systems, media counts, and FPGA cores across MiSTer devices, returning system IDs for game searches or launching cores without a game.

Instructions

<use_case> List indexed gaming systems, media counts, and FPGA cores across devices. </use_case> <important_notes>

  • Covers consoles, computers, and arcade cores configured on the MiSTer.

  • Use returned system id in mister_search_games, or pass to mister_launch to load a core with no game. </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_list_systems"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
systemsYes
unavailableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/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 real context beyond that: it says the listing covers consoles, computers, and arcade cores configured on the MiSTer, and that the returned payload includes system ids and media counts, though it says nothing about empty results or device reachability.

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?

Two short, front-loaded blocks with the purpose first and the routing notes second; every sentence carries information and there is 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?

This is a simple, single optional-parameter read tool with an output schema, so return-value details are unnecessary in the description. The definition covers scope and downstream use adequately, with only minor gaps around what an empty or unreachable-host result looks like.

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 description coverage is 100% and the single 'host' parameter is fully documented in the schema, including the 'omit when a ref already names it' rule. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 ('List indexed gaming systems, media counts, and FPGA cores') and scopes it ('across devices'), which is enough to separate it from siblings like mister_list_nfc or mister_get_status without opening the schema.

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?

The important_notes give concrete downstream routing: feed the returned system id into mister_search_games, or pass it to mister_launch to load a core without a game. That is clear usage context, but there is no explicit when-not-to-use or a named alternative list tool to choose between.

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