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

getUserEvents

Read-onlyIdempotent

The user's clicks, typing and navigations as text, one per line: [M:SS #index] click on <element> at x,y with its CSS selector; a click a script fired is marked. The getDetails timeline already lists these: call this for selectors, positions and typed values.

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

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.
llm_modelNoYour exact model id from your system prompt, or "unknown". Never guess.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 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."
    • 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.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds real behavioral detail beyond that: the per-line `[M:SS #index]` format, inclusion of CSS selectors and coordinates, and the marking of script-fired clicks — output shape an agent could not infer from structured fields.

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?

Front-loaded with the return payload, then the disambiguation. Two sentences, no filler. The clause about getDetails is slightly compressed but still readable.

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 compensates well by describing the returned text line format. It omits pagination behavior and the 200-event default, but those live in the schema, so nothing critical is missing for correct invocation.

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 100%, so all eight parameters (including fromMs/toMs, limit, format and the `after` cursor) are already documented in the schema. The description adds only indirect hints — 'typed values' and 'positions' gesture at the content, but it explains nothing about time windows or pagination beyond what the schema says.

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 the exact resource — the user's clicks, typing and navigations — and gives a concrete line format, so an agent knows precisely what comes back. It differentiates from the sibling getDetails by noting that timeline only summarizes these events, though it does not distinguish itself from getEvents.

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?

It supplies a direct routing rule: getDetails already lists the events, so call this one specifically for CSS selectors, click positions and typed values. That is explicit when-to-use-plus-alternative guidance; only an explicit exclusion case is missing.

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