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_live_logs

Filter and extract emulator logs by subsystem and severity to isolate rendering or core issues during live diagnostics.

Instructions

Filter and extract emulator logs by subsystem (e.g. Render.Vulkan, Core.ARM) and severity.

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

Input Schema

NameRequiredDescriptionDefault
severityNoSeverity level.Warning
max_linesNoMax lines to return.
subsystemNoLog subsystem filter or 'all'.all
emulator_dirNoOptional path to emulator base directory.

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?

No annotations are supplied, so the description carries the full behavioral burden, and it discloses little: it does not say the operation is read-only, whether an emulator must be running, whether results are a snapshot of a bounded buffer, or how truncation behaves. The default severity of Warning is behaviorally significant (it suppresses Trace/Debug/Info) and is never surfaced in the prose.

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 with no filler; the resource and both filter dimensions appear immediately. Nothing in it is redundant with the title or wasteful.

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?

With no annotations and no output schema, the description should do more to explain what a returned log line set looks like and how defaults shape results. All four parameters are documented in the schema, so it is not inadequate, but the default-severity filtering behavior is an important omission.

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 description coverage is 100%, so the baseline is 3. The description does add real value by giving concrete subsystem naming conventions (Render.Vulkan, Core.ARM) that the schema's generic "Log subsystem filter or 'all'" omits, but it says nothing about severity semantics or the max_lines cap.

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?

"Filter and extract emulator logs by subsystem ... and severity" states a concrete verb pair and resource plus the two filter axes, so the agent knows exactly what it retrieves. It stops short of distinguishing itself from siblings such as emulator_get_status or emulator_diagnose_game, which could also surface diagnostic information.

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 guidance, no exclusions, and no mention of alternatives for log inspection versus performance or defect tools. The agent must infer usage entirely from the filter parameters.

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