Skip to main content
Glama

events_around

Fetches raw events within a time window around a timeline timestamp to correlate nearby clicks, requests, console errors, and other interactions with an utterance.

Instructions

Raw events within a time window. t_ms = timeline ms, radius_ms default 3000, kinds = comma list (click,req,res,console,error,mut,mark,nav,say,scroll,shot)

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": {
      "t_ms": "<t_ms>"
    },
    "name": "events_around"
  }
}

Input Schema

NameRequiredDescriptionDefault
t_msYes
kindsNo
radius_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It does disclose the default radius (3000 ms) and the full taxonomy of event kinds, which is useful. However, it says nothing about result ordering, volume limits or truncation, or what happens when the radius extends past session bounds — important for a raw-event query that can return large payloads.

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?

Two compact clauses with the core purpose front-loaded and parameter glossary following. Every token carries information — defaults and the kind enumeration are packed efficiently with no filler.

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?

No output schema and no annotations mean the description is the only documentation, yet it never describes the shape of a returned event (fields, ordering, whether results are capped). For a query tool whose output is raw structured events, that omission leaves a meaningful gap even though the inputs are well covered.

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 description coverage is 0%, so the description must define the parameters, and it does: t_ms is timeline milliseconds, radius_ms defaults to 3000, and kinds is a comma-separated list with an explicit value set that the schema lacks entirely. It stops short of specifying accepted formats for invalid or unknown kind values, so it is not fully exhaustive.

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 gives a specific verb-resource pair: retrieving 'Raw events within a time window.' That scope is distinguishable from siblings like get_errors, list_says, and segment_detail, which target derived or filtered views. It doesn't explicitly name or contrast those siblings, which keeps it at 4 rather than 5.

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?

There is no explicit statement of when to use this tool instead of get_errors, get_dom_state, or list_says. The phrase 'within a time window' only implies that the caller must anchor on a timeline position. No when-not guidance or prerequisites are given.

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