Skip to main content
Glama
Sign In

Jam

by dev.jam.mcp
OverviewDiscussionsAdmin
This connector has been deprecated

Replaced by Jam.

dev.jam/jam is the official one

getConsoleLogs

Read-onlyIdempotent

The Jam's console output as text, one message per line: [M:SS #index] level: message, with the stack trace and source under it. logLevel (['error','warn'] for problems) and limit filter server-side; the first line gives the match count, and a More: line the cursor for the next 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": {
      "jamId": "<jamId>"
    },
    "name": "getConsoleLogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
toMsNoOnly events at or before this ms into the recording
afterNoFrom the previous page's `More:` line
jamIdYesJam identifier — a UUID or a jam.dev URL
limitNoMax events, default 200
formatNo'json': the rows with every stored column, for digging into one event or window
fromMsNoOnly events at or after this ms into the recording
intentNoIn 15-30 English words, your larger task and why this call helps it. People by role ("a customer"); no argument values or secrets.
logLevelNoe.g. ['error','warn']
llm_modelNoYour exact model id from your system prompt, or "unknown". Never guess.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / after / description
      Previous value: -"The previous page's nextCursor"New value: +"From the previous page's `More:` line"
    • addedInput schema / properties / format
      Added value: +{
+  "description": "'json': the rows with every stored column, for digging into one event or window",
+  "enum": [
+    "text",
+    "json"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / fromMs
      Added value: +{
+  "description": "Only events at or after this ms into the recording",
+  "minimum": 0,
+  "type": "integer"
+}
    • changedInput schema / properties / intent / description
      Previous value: -"In 15-30 words, say what larger task you are working on and why this tool helps it. Refer to people and companies by role (\"a customer\"), and leave out argument values and secrets. Use English. Example: \"Debugging a checkout failure a customer reported, checking which network request returned the 500.\""New value: +"In 15-30 English words, your larger task and why this call helps it. People by role (\"a customer\"); no argument values or secrets."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of events to return"New value: +"Max events, default 200"
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / llm_model / description
      Previous value: -"The exact model identifier you are running as, from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Pass \"unknown\" if you are not certain; never guess."New value: +"Your exact model id from your system prompt, or \"unknown\". Never guess."
    • changedInput schema / properties / logLevel / description
      Previous value: -"Optional filter by log levels, e.g. ['error','warn'] for problems."New value: +"e.g. ['error','warn']"
    • addedInput schema / properties / toMs
      Added value: +{
+  "description": "Only events at or before this ms into the recording",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent read, so the description correctly spends its space on behavior the annotations cannot convey: server-side filtering, a leading match-count line, and a `More:` line carrying the next-page cursor. It does not discuss default ordering or what happens with an expired cursor, which is a minor residual gap.

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 sentences, front-loaded with the output format and then filtering/pagination, with no filler. The inline format template is dense but earns its space; a slightly cleaner split between format and controls would help readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing returns and does so convincingly (line format, stack trace, match count, cursor). For a nine-parameter tool it leaves the time-window params and the meta params (intent, llm_model) undiscussed, though the schema documents them.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: it explains the `More:` cursor workflow for `after`, that logLevel/limit are applied server-side (not client-side truncation), and the shape of the output column layout. It says nothing about fromMs/toMs time-window semantics, though the schema covers those.

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?

The description names a specific resource (the Jam's console output) and states the exact rendered format, so an agent knows this returns browser console messages rather than network events or video frames. It never explicitly contrasts itself with getEvents or getNetworkRequests, which is the only thing keeping it from a 5.

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?

Usage is implied rather than stated: filtering with logLevel for problems and using `after` for paging tells the agent how to query, but there is no when-to-use/when-not guidance and no named alternative (e.g. getEvents or getNetworkRequests) for adjacent data needs. The agent must infer the boundary from sibling names alone.

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

All Jam toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources