[FEATURE REQUEST] Add some nice to have tools.

[thegreyfellow]

List of tools:

Description:

Some nice to have tools that would complement the full cycle of documents/collection creation/update/archive, while still adhering to the principle of minimal access, to avoid LLM mistakes or prompt injections.

Document Restoration (/documents.restore)

• Archiving is implemented, but without restore, archived documents are effectively "lost" to LLMs. If a user accidentally archives something or needs to reference it, LLMs could restore it safely (assuming the API key has permission).
• This is restorative, not destructive, and aligns with minimal risk—it's like an
  "undo" for archives.

Event Logging (/events.list)

• This read-only endpoint lists recent events (e.g., document updates, user actions). It could help LLMs track activity for summaries or notifications, like "Recent changes in the collection."
• It's metadata-only, enhancing awareness without modifications, and makes the LLMs decisions smarter by providing context they can use to respond more intelligently.

Revision History Tracking (/revisions.info and /revisions.list)

• Revisions provide an audit trail of edits, including who made changes and when—valuable for LLMs to explain document evolution, suggest improvements, or answer questions like "What changed in this doc last week?"
• This is also read-only and low-risk, as it doesn't modify data. Without it, LLMs are blind to historical context, limiting their ability to provide informed responses in collaborative or iterative workflows.

@mmmeff I would love to hear your opinion on this, and I can take this task myself :)