Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_cookies

Read-only

Read cookies for a page, optionally filtered by URL, to inspect session and authentication state in an Electron app.

Instructions

Read cookies for the page (optionally filtered by URL)

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

Input Schema

NameRequiredDescriptionDefault
urlsNo
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

C2.9/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description carries a lighter burden, but it adds almost nothing beyond that: no statement about which cookies are returned (httpOnly, session, cross-origin, all frames) or whether results include metadata like domain/expiry. The only real disclosure is that retrieval is scoped to the page.

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 short sentence with the scope front-loaded and the optional filter parenthetical placed where it is immediately useful. No filler or redundancy.

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 three-parameter read tool with no output schema and low schema description coverage, the description should indicate the shape of returned cookies and clarify how targetId versus processId select the target. Neither gap is addressed, leaving the agent to guess about both targeting and return values.

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 only 33% — processId is documented, urls and targetId are not. The phrase "optionally filtered by URL" does explain the urls array well enough to compensate partially, but targetId is left entirely unexplained in both description and schema.

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?

"Read cookies for the page" gives a specific verb (Read) and resource (cookies), with the scope limited to the current page and an optional URL filter. This clearly separates it from a mutation sibling like delete_cookie, though it does not name that sibling explicitly.

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 or when-not-to-use guidance, no mention of prerequisites such as attaching to a page first, and no pointer to related tools like get_storage or delete_cookie. The parenthetical about optional URL filtering is a capability note, not usage 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