Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Console Logs

get_console_logs

Retrieve buffered console logs since a tab spawned to diagnose misbehaving pages. Use as a first-line check for errors and messages when page behavior is unexpected.

Instructions

Buffered console output since tab spawn. First-line check when page misbehaves.

Ex: get_console_logs('t0') → {"_untrusted":true,"logs":[{"level":"error","text":"..."}]}

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": {
      "tab_id": "<tab_id>"
    },
    "name": "get_console_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_nNo
tab_idYes
force_refreshNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that output is buffered since tab spawn and shows a sample return containing _untrusted, but it does not explain log truncation, refresh behavior, or retention limits.

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?

Very concise and front-loaded: the core resource/scope comes first, followed by a useful diagnostic guidance sentence and a compact return example. No wasted text.

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?

The output schema exists, and the example gives return-shape context, but the lack of annotations and 0% schema coverage leaves optional parameters and log retention behavior underexplained. It is callable with the required tab_id, but not fully specified for all parameters.

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 0%, so the description should compensate. The example only illustrates tab_id; max_n and force_refresh are never explained, leaving two of three parameters semantically undocumented.

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?

States a specific resource and scope: buffered console output since tab spawn. It is clearly distinguishable from network and DOM tools by resource, though it does not explicitly name siblings such as clear_logs or get_network_requests.

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 clear usage context: 'First-line check when page misbehaves.' It does not state when to use alternatives like get_network_requests or when not to use this tool, but the primary diagnostic use case is explicit.

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