ATOMSATOMSDocs
Tool Reference

atoms_get_history

Audit trail for an item: who changed what, when

Retrieve the audit trail for a specific item, showing every change event with timestamps, actors, and which fields were modified. The actor field distinguishes human edits from AI-generated changes.

Parameters

ParameterTypeRequiredDescription
project_idstring (UUID)YesThe project containing the item
item_idstringYesThe item to get history for (e.g., REQ-001, TC-050)
limitnumberNoMax entries to return (1-100). Default: 20

Example Response

{
  "status": "success",
  "data": [
    {
      "event_type": "updated",
      "changed_by": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "changed_at": "2025-04-12T14:32:00Z",
      "actor": "user",
      "session_id": null,
      "fields_changed": ["title", "body"]
    },
    {
      "event_type": "created",
      "changed_by": "f9e8d7c6-b5a4-3210-fedc-ba0987654321",
      "changed_at": "2025-04-10T09:15:00Z",
      "actor": "mcp_claude",
      "session_id": "sess_abc123",
      "fields_changed": ["title", "body", "domains", "level"]
    }
  ]
}

Notes

  • This tool is read-only and does not modify any data (readOnlyHint: true).
  • The actor field returns "user" for changes made through the ATOMS web app and "mcp_claude" for changes made via the MCP integration.
  • When actor is "mcp_claude", the session_id field identifies which AI session made the change.
  • Results are ordered by changed_at descending (most recent first).
  • Use the limit parameter to control how many history entries are returned. The default of 20 is sufficient for most audit reviews.

On this page