Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

emulate

Configure device metrics, user agent, geolocation, and media settings for Electron app debugging; use clear to reset overrides.

Instructions

Device metrics / UA / geolocation / media emulation (or clear=true to reset)

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

Input Schema

NameRequiredDescriptionDefault
clearNo
mediaNoe.g. "print" or "screen"
metricsNo
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.
userAgentNo
geolocationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations supply only destructiveHint=false, so the description carries nearly the full behavioral burden. It does disclose that clear=true resets emulation (a trait absent from annotations and from the schema's undocumented 'clear' property), but says nothing about scope (per-target vs. global), persistence across navigations, or whether emulation must be re-applied after reload.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded line with no filler, and the reset option is placed where an agent will see it. It is arguably over-compressed rather than padded, but no sentence is wasted.

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

Completeness2/5

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

For a 7-parameter tool with nested metric objects, no output schema, and annotation coverage limited to destructiveHint, this one line is not enough. Missing are target selection semantics, persistence/reset scope, and what happens when emulation is partially applied.

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 29% across 7 parameters, so the description partly compensates by naming the four emulation domains that map to metrics, userAgent, geolocation, and media, and by flagging clear=true as the reset switch. It says nothing about targetId vs. processId (the processId schema hint is the only target-selection guidance) or about combining domains in a single call.

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?

Names four concrete emulation domains (device metrics, UA, geolocation, media) plus a reset mode, so an agent knows it is a browser/device emulation control rather than a network emulator. It does not name the sibling emulate_network or state the boundary between the two, so differentiation is only implied by the word 'device'.

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?

The only usage signal is '(or clear=true to reset)', which tells how to undo emulation but not when to apply it, in what order relative to navigation, or whether a target must be selected first. No exclusions or alternatives are given, and the presence of emulate_network in the catalog makes the missing routing hint a real gap.

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