Skip to main content
Glama
Sign In
MiSTerClaw

MiSTerClaw

by catallo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

mister_osd_info

Retrieve the OSD menu structure for any MiSTer core. Displays parsed CONF_STR items such as options, triggers, file loaders, and sub-pages to clarify core settings and OSD navigation.

Instructions

Get the OSD (On-Screen Display) menu structure for the currently loaded core or a specified core. Returns the parsed CONF_STR menu items including options, triggers, file loaders, and sub-pages. Useful for understanding what settings a core supports and what the OSD menu looks like.

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_osd_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
coreNoCore name to look up (e.g. 'SNES', 'Genesis', 'NES'). If omitted, uses the currently loaded core.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses that it returns parsed CONF_STR menu items with options, triggers, etc., but does not mention side effects, read-only nature, or performance implications.

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 concise sentences: first states purpose, second details return content. No fluff, every sentence is informative.

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 simple tool with one optional parameter and no output schema, the description adequately explains what is returned. Could mention if there are any limitations or dependencies on core loading.

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 coverage is 100% with a detailed parameter description. The description adds minimal extra meaning beyond the schema, only restating that the core can be specified or defaults to current.

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?

Description clearly states it retrieves OSD menu structure for a core, using specific verbs ('Get', 'Returns'). It distinguishes from sibling tools like mister_osd_navigate and mister_osd_visible by focusing on information retrieval.

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 description explains when to use ('useful for understanding what settings a core supports'), but does not mention when not to use or alternatives, such as other OSD-related tools.

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