Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

page_info

Read-only

Retrieve page metadata—URL, title, readyState, and userAgent—to inspect an Electron target and verify page readiness.

Instructions

Get URL, title, readyState, and userAgent for a page target

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

Input Schema

NameRequiredDescriptionDefault
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, and the description usefully enumerates the four returned fields, which matters because no output schema exists. However, it says nothing about error behavior when the target is missing, what readyState values mean, or whether the call blocks.

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 that lists the resource and its return fields with zero filler. Nothing could be removed without losing information.

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?

For a two-parameter read tool, the description covers the return payload well (important with no output schema) but leaves targetId semantics entirely undefined. An agent can call it with zero args, but cannot reason about targeting a specific page in a multi-target app.

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 but targetId has no description anywhere. The description does not compensate — it never explains what a targetId is, how to obtain one, or when to supply it versus omitting it.

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 names a specific verb ('Get') and enumerates exactly what is retrieved: URL, title, readyState, and userAgent for a page target. The scope is unambiguous, though it never names a sibling tool or explains how it differs from broader inspection tools like assert_ui or evaluate.

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 preconditions (e.g. page must be attached), and no mention of alternatives. The agent must infer from the name alone that this is the lightweight page-metadata read versus heavier UI evaluation or assertion tools.

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