Skip to main content
Glama
Sign In
Switch 2 Emulator Diagnostics MCP Server

Switch 2 Emulator Diagnostics MCP Server

by JayceeB1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

emulator_get_status

Retrieve live emulator runtime status, including active title, uptime, CPU/RAM usage, and Vulkan GPU backend, to diagnose performance and rendering issues.

Instructions

Get current emulator runtime status, active title, uptime, CPU/RAM, and Vulkan GPU backend.

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": "emulator_get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
emulator_dirNoOptional path to emulator base directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Get current ... status' implies a non-mutating read and the enumerated fields give a rough picture of the payload, but nothing is said about behavior when no emulator is running, whether one must be started first, or whether the call is expensive.

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?

One front-loaded sentence with zero filler; the verb and scope lead and the return inventory follows. Nothing could be removed without losing information.

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 one-parameter read tool with no output schema, enumerating the returned values is the right compensating move. The only real gap is the unstated default for emulator_dir and the lack of any emulator-running precondition.

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?

There is a single optional parameter with 100% schema coverage, and the schema already explains emulator_dir. The description adds nothing about it, notably not what happens when it is omitted (which directory is assumed), so the high-coverage baseline of 3 applies.

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?

Specific verb 'Get' plus resource 'emulator runtime status', with the returned fields (active title, uptime, CPU/RAM, Vulkan GPU backend) enumerated. This distinguishes it from log- or screenshot-oriented siblings, but the overlap with emulator_get_performance (CPU/RAM) is never addressed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use, when-not-to-use, or alternative is stated; the description is purely a content list. An agent must infer that this is the general status snapshot and guess how it differs from emulator_get_performance.

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