Skip to main content
Glama
Sign In
Electron Stagewright

Electron Stagewright

by electron-stagewright
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Electron app info

electron_info
Read-only

Reports the running Electron app's environment: runtime versions, app name and paths, packaged and code-signature status, active transport, and capability matrix. Target a specific session by passing sessionId.

Instructions

Report the running Electron app environment: runtime versions (electron/node/chrome/v8), app name/version/paths, packaged flag, code-signature status (verified for packaged macOS apps; "unknown" for unpackaged/dev apps, "unsupported" off macOS), the active transport, and its capability matrix. Pass sessionId to target a specific session when several are running. Versions and app fields are null when the transport cannot evaluate in the main process (CDP sessions). Returns: { ok, session_id, transport, versions, app, signature, capabilities }. Errors: NOT_RUNNING (no session — call electron_launch first; not retryable), BAD_ARGUMENT (multiple sessions live — pass sessionId; not retryable).

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

Input Schema

NameRequiredDescriptionDefault
sessionIdNoTarget session id. Omit when a single session is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0
  2. Removedv0.4.1
  3. First observedv0.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds substantial undisclosed behavior: signature status semantics per packaging and OS, null returns for versions/app under CDP transports, and error codes with explicit retryability. This is exactly the kind of context structured fields cannot convey.

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 dense but well-ordered paragraph: purpose first, then enumeration, then the targeting rule, then return shape, then errors. No filler sentences, and every clause carries information an agent would otherwise have to probe for.

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

Completeness5/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 supplies the return object shape and the error taxonomy itself, plus the null-field caveats for CDP sessions. For a read-only diagnostic tool, nothing an agent needs to call it correctly or interpret the result is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the single sessionId parameter is already documented; the description still adds meaning by tying omission to the single-session case and by naming the BAD_ARGUMENT failure when multiple sessions are live. Marginal but genuine added value above baseline 3.

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

Purpose5/5

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

States a specific verb ('Report') and resource ('running Electron app environment') and then enumerates exactly what is reported: versions, app identity/paths, packaged flag, code-signature status, transport, and capability matrix. An agent can distinguish this from sibling probes like electron_status or electron_discover_running from the content list alone.

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

Usage Guidelines4/5

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

Gives a concrete conditional ('Pass sessionId to target a specific session when several are running') and routes the NOT_RUNNING case to electron_launch first. It stops short of naming a sibling as the preferred alternative for, say, a quick liveness check, so it is clear context rather than full when/when-not routing.

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