Skip to main content
Glama
stevepridemore

Graph-Memory

by stevepridemore
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Dream Audit Log

graph_audit

Logs structured events to an audit trail for dream process, tracking entity resolution decisions to enable later reconstruction of merges.

Instructions

Append a structured event to the dream process audit log (logs/dream-audit.jsonl). Call this during the dream process to record run_start, run_end, transcript_start, transcript_end, entity_created, entity_resolved, edge_created, edge_modified, merge_flagged, contradiction_found, ingest_start, ingest_end, decay_applied, format_warning, or error events. entity_resolved is the audit trail for entity-resolution decisions during dream — every time the dream picks between matching an existing entity, creating a new one, or flagging an ambiguous candidate, log it here so a later graph_unmerge can reconstruct why a merge happened.

Input Schema

NameRequiredDescriptionDefault
dataYesEvent payload — fields vary by event type. Always include relevant names/IDs.
eventYesEvent type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2
  2. Removedv0.1.4
  3. Changed1 schema field changedv1.0.3
    • changedInput schema / properties / event / enum
      Previous value: -[
-  "run_start",
-  "run_end",
-  "transcript_start",
-  "transcript_end",
-  "transcript_skipped",
-  "entity_created",
-  "edge_created",
-  "edge_modified",
-  "merge_flagged",
-  "contradiction_found",
-  "ingest_start",
-  "ingest_end",
-  "decay_applied",
-  "format_warning",
-  "error"
-]New value: +[
+  "run_start",
+  "run_end",
+  "transcript_start",
+  "transcript_end",
+  "transcript_skipped",
+  "entity_created",
+  "entity_resolved",
+  "edge_created",
+  "edge_modified",
+  "merge_flagged",
+  "contradiction_found",
+  "ingest_start",
+  "ingest_end",
+  "decay_applied",
+  "format_warning",
+  "error"
+]
  4. First observedv1.0.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations present, so description carries full burden. It discloses the append-only action and log file path. However, it does not mention idempotency, concurrency behavior, or error handling (e.g., what happens on duplicate events). Adequate for a simple logging tool but could be more thorough.

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 dense sentences pack all essential info: action, target file, event types, and data guidance. No filler or redundancy.

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

Completeness5/5

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

For a logging tool with no output schema, the description is complete: it specifies the action, file location, event types, data expectations. All necessary context for correct invocation is present.

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 covers both parameters fully. Description adds value by explaining that data fields vary by event type and advising 'Always include relevant names/IDs,' which aids correct usage beyond schema definitions.

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?

Description clearly states the tool appends events to a specific audit log, lists 16 event types, and highlights entity_resolved's role. This specificity and verb+resource clarity distinguish it from sibling tools like graph_boost or graph_merge.

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?

Explicitly says 'Call this during the dream process' and enumerates events. Provides context but no exclusion criteria or alternatives (e.g., when to skip logging). The description implies usage but doesn't fully guide when not to use.

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