remnus

get_changes_since

Read-only

Get a compact list of everything that changed in the workspace since a given time or a previous call's cursor — pages/databases edited, database rows edited, and items deleted. Built for recurring agents (daily report, standup, memory refresh) so they can sync incrementally instead of re-reading the whole workspace every run. Omit both since and cursor to bootstrap a full crawl, saving the returned nextCursor (or the latest updatedAt) for the next call.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum changes per page (default 100)
`since`	No	ISO 8601 timestamp — only return changes after this time (e.g. "2026-07-01T00:00:00Z"). Ignored when cursor is provided. Omit both for a full crawl.
`cursor`	No	Pagination cursor from a previous response's nextCursor field — takes priority over since for resuming a sync

Output Schema

TableJSON Schema

Name	Required	Description
`changes`	Yes	Chronological, oldest first
`hasMore`	Yes
`nextCursor`	No	Pass back as cursor to continue or resume a later sync

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedJul 8, 2026

changedOutput schema / properties / changes / description

Previous value: -"Changes in chronological order (oldest first)"New value: +"Chronological, oldest first"

changedOutput schema / properties / changes / items / properties / databaseId / description

Previous value: -"Parent database ID, present for database_row entries"New value: +"Present for database_row entries"

changedOutput schema / properties / changes / items / properties / id / description

Previous value: -"Item ID (pass to get_page or query_database)"New value: +"Pass to get_page or query_database"

removedOutput schema / properties / changes / items / properties / title / description
```
Removed value: -"Item title (last known title for deleted items)"
```

removedOutput schema / properties / changes / items / properties / updatedAt / description

Removed value: -"When the change happened (ISO 8601) — for \"deleted\", when the deletion happened"

removedOutput schema / properties / hasMore / description

Removed value: -"Whether more changes exist beyond this page"

changedOutput schema / properties / nextCursor / description

Previous value: -"Cursor for the next page (present when hasMore) — also use this to resume a later sync from where this call left off"New value: +"Pass back as cursor to continue or resume a later sync"

AddedJul 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description adds value by detailing what the tool returns (pages/databases edited, database rows edited, items deleted) and explaining cursor behavior. It provides sufficient behavioral context beyond the annotations.

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?

The description is concise and front-loaded with the core purpose. Two sentences efficiently convey the tool's functionality and usage pattern, with no redundant information.

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?

Given the tool has an output schema (not shown) and is relatively simple with only three optional parameters, the description is complete. It covers the primary use case, parameter relationships, and initialization flow, meeting the agent's needs for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides full descriptions for all three parameters, but the description adds critical semantic context: the priority of cursor over since, the effect of omitting both for a full crawl, and the mention of return fields (nextCursor, updatedAt). This significantly enhances the agent's understanding beyond the schema.

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 clearly states the tool's purpose: retrieving a compact list of workspace changes since a given time or cursor. It specifies the resource (workspace changes) and action (get), and differentiates from siblings by emphasizing incremental syncing, which is unique among the listed tools.

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?

The description explicitly states it is built for recurring agents to sync incrementally and explains when to use the `since` vs `cursor` parameters, including bootstrapping a full crawl. However, it does not explicitly mention when not to use the tool, such as for ad-hoc queries where other tools like query_database or search_workspace might be more appropriate.

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

All remnus tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.