Skip to main content
Glama
Sign In
SuperDev

SuperDev

by Xsxdot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Browser console logs

browser_console_logs
Read-only

Retrieve recent browser console logs from a debug session to diagnose runtime issues. Filter by log level (log, info, warning, error) and set a limit up to 200 entries.

Instructions

Read recent console logs captured from a browser debug session page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "browser_console_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNo
limitNo
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, and the description consistently says 'Read', so there is no contradiction. The description adds context about the source ('browser debug session page') but doesn't disclose recency limits or whether reading consumes the logs.

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?

The description is a single, front-loaded sentence with no redundant details. It efficiently states the action, object, and context.

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?

There is no output schema, so the description should explain return values, but it doesn't. It also doesn't clarify that session_id refers to an active debug session or how 'recent' is interpreted, leaving the agent to infer critical operational details.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention any of the three parameters (session_id, level, limit). The agent receives no semantic guidance beyond the names and types in the schema.

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?

The description uses a specific verb ('Read') and resource ('recent console logs') with a clear scope ('captured from a browser debug session page'). This clearly distinguishes it from siblings like browser_network_requests or tail_logs.

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

Usage Guidelines3/5

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

The description implies usage context (when you need console logs from a browser debug session), but it does not explicitly state when to use this tool vs alternatives like tail_logs or search_logs. No exclusions or alternative guidance is provided.

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