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_performance

Measure real-time FPS, frametimes, and CPU utilization to diagnose performance bottlenecks during Switch 2 emulator gameplay.

Instructions

Measure real-time FPS, frametimes (ms), and CPU utilization.

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

Input Schema

NameRequiredDescriptionDefault
emulator_dirNoOptional path to emulator base directory.
sample_duration_secNoDuration to sample CPU load.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses very little. It does not say whether the call blocks while sampling, that sampling length is bounded by sample_duration_sec (up to 5s), whether it is a read-only non-mutating operation, or what happens if the emulator is idle — all things an agent needs before invoking it.

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?

A single front-loaded sentence naming the verb and the three measured quantities, with no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description effectively names the return values, which partly compensates for the missing output schema, and the two optional params are fully schema-documented. However, for a live-measurement tool it omits operational context such as emulator-state prerequisites and the blocking nature of sampling, leaving clear gaps.

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%, so both parameters are already documented in the schema; the description adds only the implicit link between 'CPU utilization' and the CPU-load sampling duration. Baseline 3 is appropriate since the schema does the heavy lifting.

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 description gives a specific verb ('Measure') plus the exact metrics returned: real-time FPS, frametimes in ms, and CPU utilization. That is enough to distinguish it from siblings like emulator_get_shader_stats or emulator_get_live_logs, though it never explicitly contrasts itself with them.

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?

There is no when-to-use or when-not-to-use guidance, and no stated prerequisites such as whether the emulator must be running or a game loaded for measurement to succeed. The agent must infer that this is the tool for performance measurement purely from the metric names.

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