Skip to main content
Glama
putervision

state-memory-mcp

by putervision
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_events

Read-onlyIdempotent

Inspect append-only event ledgers, query changeset diffs, and generate session post-mortems to audit workflow state changes over time.

Instructions

Inspect the append-only event audit ledger, query structured changesets, and generate session post-mortems (actions: log, changelog, post_mortem). Use get_events instead of manage_snapshots when examining the granular chronological sequence of mutations rather than restoring state checkpoints.

Returns chronological event array, structured changeset diff, or session post-mortem markdown report.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum events to return (1-1000).
sinceNoISO timestamp or relative duration (e.g. 2h, 1d) for log or changelog.
untilNoEnding ISO timestamp for log.
actionYesThe event query action to execute: log, changelog, post_mortem.
offsetNoPagination offset for log.
projectNoTarget project name or slug.
git_branchNoGit branch filter for changelog.
session_idNoSession ID for log or post_mortem.
since_sessionNoSession ID to diff from for changelog.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.1
    • changedInput schema / properties / action / description
      Previous value: -"The event query action to execute."New value: +"The event query action to execute: log, changelog, post_mortem."
    • addedInput schema / properties / action / enum
      Added value: +[
+  "log",
+  "changelog",
+  "post_mortem"
+]
  2. Changed3 schema fields changedv1.2.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -true
    • addedInput schema / required
      Added value: +[
+  "action"
+]
  3. Addedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds value by characterizing the ledger as 'append-only' (immutability of the underlying data) and by stating the shape of each action's return, which the annotations do not.

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?

Three sentences: purpose plus actions, then sibling routing, then return values. Nothing is redundant, and the routing constraint that determines tool selection is front-loaded rather than buried.

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?

For a 9-parameter read-only tool with no output schema, the description covers purpose, selection criteria, and the return format for each action, which is enough to call it correctly. It does not address pagination behavior despite log exposing limit/offset, a minor residual gap.

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 per-parameter syntax is already documented and the baseline is 3. The description goes beyond the schema by mapping each action value to a distinct output (chronological event array, structured changeset diff, session post-mortem markdown), which is semantics the enum listing alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('append-only event audit ledger'), three concrete actions (log, changelog, post_mortem), and the returned artifacts. It is immediately distinguishable from siblings like manage_snapshots, which it explicitly positions itself against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit either/or routing rule: use get_events over manage_snapshots when examining the chronological sequence of mutations rather than restoring checkpoints. The parenthetical action list also tells the agent which sub-mode to select without opening the schema.

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