Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_performance_metrics

Read-only

Fetch renderer performance metrics such as JS heap, layout count, and task duration to diagnose Electron app performance issues.

Instructions

Renderer Performance.getMetrics (JS heap, layout count, task duration, …)

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

Input Schema

NameRequiredDescriptionDefault
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.6/5.0
Behavior3/5

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

readOnlyHint=true already establishes this is a safe, non-mutating read, so the description's main added value is naming the metric families returned (JS heap, layout count, task duration), which matters since no output schema exists. However the list is truncated with an ellipsis, so it doesn't disclose the full return shape, whether metrics are cumulative counters or gauges, or whether a snapshot is taken at call time.

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

Conciseness3/5

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

It is short and front-loaded, which is good, but the brevity comes at the cost of substance — the single parenthetical with a trailing ellipsis reads as an unfinished note rather than a deliberate, complete statement.

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?

With no output schema, the description is the only place an agent can learn what comes back, and it only gestures at three example metric names. For a diagnostic tool with two parameters and one undocumented parameter, this leaves the agent guessing about return content, snapshot semantics, and parameter selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: processId is documented in the schema as falling back to the single running app, but targetId has no description anywhere. The description text says nothing about either parameter, so it does not compensate for the gap or explain how targetId and processId interact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially the underlying CDP domain/method ("Performance.getMetrics") plus a parenthetical listing measured quantities (JS heap, layout count, task duration). It tells an agent this retrieves renderer performance counters, but the verb+resource framing is inherited from the tool name rather than stated, and the trailing ellipsis leaves the scope open-ended.

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 at all. With siblings like get_process_health, diagnose, and doctor in the catalog, an agent has no statement of whether this is for renderer-level counters versus process health or general diagnosis, and no exclusions or prerequisites are given.

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