Skip to main content
Glama
dtz-labs

zesarux-mcp

by dtz-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_machine

Configure ZEsarUX to emulate a specific machine type using its ZRCP identifier.

Instructions

Set the emulated machine type in ZEsarUX (ZRCP "set-machine "). Use a real ZEsarUX machine identifier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
machineYesZEsarUX machine identifier (left column of get-machines), e.g. "48k", "128k", "TC2068", "Pentagon", "TBBlue".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • changedInput schema / properties / machine / description
      Previous value: -"Machine identifier (e.g., \"spectrum48\", \"spectrum128\", \"pentagon\", \"tbblue\")"New value: +"ZEsarUX machine identifier (left column of get-machines), e.g. \"48k\", \"128k\", \"TC2068\", \"Pentagon\", \"TBBlue\"."
    • changedInput schema / properties / machine / enum
      Previous value: -[
-  "spectrum48",
-  "spectrum48_plus",
-  "spectrum48_spanish",
-  "spectrum128",
-  "spectrum128_spanish",
-  "spectrum_plus2",
-  "spectrum_plus2_spanish",
-  "spectrum_plus2a",
-  "spectrum_plus3",
-  "spectrum_plus3_spanish",
-  "pentagon",
-  "pentagon128",
-  "pentagon512",
-  "tbblue",
-  "zxuno",
-  "tsconf",
-  "zx80",
-  "zx81",
-  "ql",
-  "z88",
-  "cpc464",
-  "cpc6128",
-  "cpc664",
-  "samcoup",
-  "msx1",
-  "sg1000",
-  "colecovision"
-]New value: +[
+  "MK14",
+  "ZX80",
+  "ZX81",
+  "16k",
+  "48k",
+  "48kp",
+  "128k",
+  "QL",
+  "P2",
+  "P2F",
+  "P2S",
+  "P2A40",
+  "P2A41",
+  "P2AS",
+  "P340",
+  "P341",
+  "P3S",
+  "TC2048",
+  "TC2068",
+  "TS1000",
+  "TS1500",
+  "TS2068",
+  "Inves",
+  "48ks",
+  "128ks",
+  "TK80",
+  "TK82",
+  "TK82C",
+  "TK83",
+  "TK85",
+  "TK90X",
+  "TK90XS",
+  "TK95",
+  "TK95S",
+  "CZ1000",
+  "CZ1500",
+  "CZ1000p",
+  "CZ1500p",
+  "CZ2000",
+  "CZSPEC",
+  "CZSPECp",
+  "Z88",
+  "Sam",
+  "Pentagon",
+  "Chloe140",
+  "Chloe280",
+  "Chrome",
+  "Prism",
+  "ZXUNO",
+  "BaseConf",
+  "TSConf",
+  "TBBlue",
+  "ACE",
+  "CPC464",
+  "CPC4128",
+  "CPC664",
+  "CPC6128",
+  "PCW8256",
+  "PCW8512",
+  "MSX1",
+  "Coleco",
+  "SG1000",
+  "SMS",
+  "SVI318",
+  "SVI328"
+]
  2. First observedv1.0.1

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, state changes, or required permissions. It merely restates the operation without explaining that changing the machine type may reset emulator state or invalidate loaded content.

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 description is extremely concise at two sentences, with no unnecessary words. It front-loads the primary action and includes a brief note on parameter validation. Every sentence earns its place.

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?

Given the tool's simplicity (one parameter, no output schema), the description is adequate. It covers what the tool does and how to use the parameter. However, it could mention that changing the machine type may affect the emulation state, but that is not critical for a straightforward setter.

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?

The schema provides full coverage with enum values and examples. The description adds value by instructing to use a 'real ZEsarUX machine identifier' and referencing 'get-machines', which guides the agent to choose a valid value. This exceeds what the schema alone offers.

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 clearly states the tool's purpose: 'Set the emulated machine type in ZEsarUX'. It uses a specific verb ('Set') and resource ('emulated machine type'), and distinguishes itself from sibling tools like 'reset_machine' by focusing on changing the machine type rather than resetting.

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?

The description implies usage when the user wants to change the machine type, but it does not explicitly state when to use this tool versus alternatives like 'reset_machine' or 'get_emulator_info'. No exclusions or prerequisites are mentioned.

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