Skip to main content
Glama

console_log

Retrieve recent game console output, optionally filtered by regex, to inspect PanoramaScript or JavaScript exceptions and debug live Deadlock UI behavior.

Instructions

Recent game console output (from console.log), optionally regex-filtered, e.g. pattern='PanoramaScript|JS Exception|panorama'.

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

Input Schema

NameRequiredDescriptionDefault
linesNo
patternNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully reveals the data source (console.log) and that filtering is regex-based, but says nothing about whether this blocks, what happens if the log file is missing, whether the pattern is case-sensitive, or whether output is tailed vs. a snapshot.

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?

Two compact lines, front-loaded with the resource and then the optional filter, with no filler. The inline regex example earns its space by demonstrating filter syntax.

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?

An output schema exists, so return values need no explanation, and the tool is low-complexity with two optional parameters. Still, one of those parameters is undocumented and no operational context (game running, log existence, error behavior) is supplied, leaving the definition only marginally adequate.

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 coverage is 0%, so the description must compensate. It does well for 'pattern' by giving a concrete regex example ('PanoramaScript|JS Exception|panorama'), but 'lines' is never mentioned at all — an agent must infer from the bare name and default of 100 that it controls how many recent lines are returned.

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 verb-and-resource pair: it returns recent game console output sourced from console.log. That is clearly distinguishable from siblings like js_eval or status, though the description never explicitly contrasts itself with any of them.

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?

The only usage signal is 'optionally regex-filtered', which hints at a common case but gives no when-to-use context, no prerequisites (e.g. whether the game must be launched or a log file must exist), and no pointer to any alternative tool for related diagnostics.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.