Skip to main content
Glama

Read MiSTer.ini

mister_get_ini
Read-only

Read sections and key-value pairs from MiSTer.ini configuration files on MiSTer SD storage over root SSH, returning one section or all settings for global and per-core overrides.

Instructions

<use_case> Read sections and key-value pairs from MiSTer.ini configuration files on SD storage. </use_case> <important_notes>

  • Requires root SSH access to the device.

  • [MiSTer] section is global; core sections (e.g. [SNES]) provide per-core overrides. </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_ini"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoMiSTer.ini, or an alternate such as MiSTer_crt.ini (mister_get_ini lists them).MiSTer.ini
hostNoMiSTer name from mister_get_status. Omit when the call already says which (a ref does).
sectionNoOnly this section, e.g. MiSTer or SNES. Omit for all.

Output Schema

NameRequiredDescriptionDefault
fileYes
hostYes
filesYes
sectionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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, and the description adds real context beyond them: the root SSH prerequisite and the structural distinction between the global [MiSTer] section and per-core override sections. It does not cover failure modes such as a missing or malformed ini file, which keeps it below a 5.

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?

The definition is two short, tagged blocks with zero filler; the core purpose is front-loaded and the caveats follow. Every line carries actionable information for an agent.

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, return values need not be explained, and the annotations cover the safety profile. Prerequisites and section semantics are supplied, leaving only error behavior (missing file, permission failure) unaddressed for this simple read tool.

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?

Schema coverage is 100%, so the baseline is 3, but the notes add genuine meaning for the section parameter by explaining that [MiSTer] is global while core sections like [SNES] supply per-core overrides. That helps an agent decide whether to pass a section at all, going beyond the schema's terse 'Only this section' text.

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 use_case states a specific verb and resource: read sections and key-value pairs from MiSTer.ini on SD storage. An agent can immediately tell this is a read operation against configuration files, and the presence of mister_set_ini as a sibling is implicitly contrastable. It stops short of explicitly naming the write counterpart, so it is clear but not maximally differentiated.

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 implied by the use_case and the important_notes give prerequisites (root SSH access), but there is no explicit statement of when to call this versus a sibling such as mister_set_ini or mister_get_status. The agent must infer the trigger condition from the tool name and description alone.

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