Skip to main content
Glama

Search for games

mister_search_games
Read-only

Search MiSTer FPGA game libraries by name and optional system, returning launchable game references for subsequent launch calls.

Instructions

<use_case> Search for games across MiSTer FPGA libraries by name query and optional system filter. </use_case> <important_notes>

  • Returns launchable game refs (e.g. 'Family Room/4812').

  • The ref encapsulates target host and mediaId for subsequent mister_launch calls.

  • variant differentiates region/revision/hack versions. </important_notes>

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": {
      "query": "<query>"
    },
    "name": "mister_search_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoMiSTer name from mister_get_status. Omit when the call already says which (a ref does).
limitNoMost results per MiSTer.
queryYesWords in the game's name, e.g. 'metroid'.
systemNoA system id from mister_list_systems, e.g. 'SNES' or 'Genesis'.

Output Schema

NameRequiredDescriptionDefault
resultsYes
truncatedYes
unavailableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true) and closed world, so the bar is lower. The description adds real value on top: it explains that results are refs like 'Family Room/4812', that a ref encapsulates host plus mediaId, and that 'variant' distinguishes region/revision/hack versions — all behavioral context absent from the annotations.

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 XML-tagged structure front-loads the use case and keeps the notes to three tight bullets with no filler. Slight redundancy between the use_case line and the parameter names ('name query and optional system filter') costs little but keeps it from a 5.

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?

With an output schema present and read-only semantics covered by annotations, the description only needs to cover workflow and result interpretation, which it does by explaining refs and the launch follow-up. It does not clarify multi-host behavior when 'host' is omitted (the 'Most results per MiSTer' phrasing hints at cross-library search without stating it), which is a minor gap for a 4-parameter search tool.

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%, with host, limit, query, and system each documented in-schema (including cross-references to mister_get_status and mister_list_systems), so the schema carries the parameter burden. The description restates the query/system semantics but adds no format or edge-case detail beyond the schema; 'variant' is described but is not one of the input parameters.

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?

The description names a specific verb and resource ('Search for games') and states the search dimensions ('by name query and optional system filter'), so an agent can distinguish it from mister_list_systems (enumeration) or mister_launch (execution) 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 notes give clear contextual guidance: results are launchable refs intended to feed 'subsequent mister_launch calls', and the schema pointers ('system id from mister_list_systems', 'host from mister_get_status') tell the agent which sibling to call first. It stops short of explicit when-not-to-use or exclusion rules, so it falls short of a 5.

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