Skip to main content
Glama

cortex_debug

Destructive

Collect compact browser-session diagnostics without console or network contents, optionally capture a local screenshot, and close an isolated session when requested.

Instructions

Diagnostica compatta senza contenuti console/rete; screenshot locale solo con screenshot=true.

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

Input Schema

NameRequiredDescriptionDefault
sessionIdNoID restituito da newSession. Omettere per usare la sessione condivisa.
screenshotNo
closeSessionNoChiude il contesto isolato indicato da sessionId, senza avviare il browser.
project_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0-dev.1

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, yet the description never mentions that the tool can close or tear down a session context, nor any side effects, auth needs, or what 'diagnostics' comprises. It does clarify that the screenshot is local and gated, which adds a little beyond annotations, but the destructive dimension is left entirely to the structured hint.

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 tight sentence with the primary purpose front-loaded and the caveat in a second clause. Nothing is redundant, though the semicolon-joined conditional is terse to the point of ambiguity.

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 destructive, open-world tool with four parameters, no output schema and only 50% schema coverage, the description is far too thin: it omits what the diagnostics contain, the session-lifecycle effects, and the meaning of project_path.

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 coverage is 50%: sessionId and closeSession are self-documented in the schema, and the description adds the one non-obvious rule for screenshot (only produces a local capture when true). project_path and the exact behavior of screenshot=false remain undocumented in both places.

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?

"Diagnostica compatta" names a resource (diagnostics) but the verb is vague — it never says what is being inspected or returned. The qualifiers (no console/network content, screenshot only with screenshot=true) do narrow the scope somewhat, but the tool is not explicitly contrasted with cortex_open, cortex_peek or cortex_run.

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 statement of when to choose this tool over cortex_open or cortex_peek, nor any precondition (e.g. whether a session must already exist). The only conditional given is a parameter constraint (screenshot=true), not usage guidance.

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