Skip to main content
Glama
Sign In

Renor

by io.github.patrickpassosb
OverviewDiscussionsAdmin

Export everything this workspace holds

export_memory
Read-onlyIdempotent

Returns everything the workspace holds, as portable Markdown (format renor-export/v1): the fact ledger exactly as stored (every fact with its subject, predicate, object, your words, source, scope, timestamps and event id, retired ones included), every daily-log entry (remember, remember_note) with its timestamp, source and scope, every other note (imports and your own notes) in full with its metadata, and everything retired and not restored (notes, entries, facts) with when it was retired. The reply is two blocks: a JSON manifest (counts per kind for a whole export, the sections it carries, whether it is complete) and the document. A workspace too large for one reply is paged, never cut: while the manifest says truncated, or has nextSection/nextItem, call again with section (ledger, daily-entries, notes, retired, and learning-log when the manifest names it) and offset (the item to continue from) until neither is set. A reply holds at most a bounded page, however large the workspace is. Not exported, and listed by kind in the manifest's notExported: the search index and embeddings (rebuilt from this), agent requests, import receipts, activity, agent connection state, the promoted history directory, and non-Markdown files.

Input Schema

NameRequiredDescriptionDefault
offsetNoThe item of that section to continue from (from the manifest's nextItem); default 0
sectionNoContinue with this section only (from the manifest's nextSection)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / section / enum
      Previous value: -[
-  "ledger",
-  "daily-entries",
-  "notes",
-  "retired"
-]New value: +[
+  "ledger",
+  "daily-entries",
+  "notes",
+  "retired",
+  "learning-log"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / section / enum
      Previous value: -[
-  "ledger",
-  "daily-entries",
-  "notes",
-  "retired",
-  "learning-log"
-]New value: +[
+  "ledger",
+  "daily-entries",
+  "notes",
+  "retired"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / section / enum
      Previous value: -[
-  "ledger",
-  "daily-entries",
-  "notes",
-  "retired"
-]New value: +[
+  "ledger",
+  "daily-entries",
+  "notes",
+  "retired",
+  "learning-log"
+]
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the two-block response shape, manifest completeness and truncation fields, page-size bounds, continuation behavior, and the explicit list of kinds that are not exported. This is unusually rich behavioral context for an agent deciding whether the export is complete or requires further calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the export result, then moves logically to response shape, paging, page bounds, and exclusions. It is dense and well organized overall, though the opening sentence is long and repeats the inclusion of retired facts later in the paragraph.

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?

With no output schema, the description carries the burden of explaining the return value, and it does so fully: manifest plus document, counts, completeness, paging semantics, and excluded data. Nothing essential for correctly invoking or continuing an export appears to be missing.

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 the schema already documents section and offset, but the description adds meaningful semantics: section values come from the manifest's nextSection, learning-log appears only when the manifest names it, and offset is the item to continue from nextItem. This goes beyond the schema's basic enum and integer descriptions.

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 states a specific verb and resource: export the entire workspace contents as portable Markdown in a named format. It enumerates exactly what is included (fact ledger, daily-log entries, notes, retired items) and excludes, making it clearly distinguishable from siblings such as read_memory, search_memory, and memory_map.

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?

It gives clear operational guidance for paging: when the manifest is truncated or has nextSection/nextItem, call again with section and offset until neither is set. It does not explicitly name alternatives like read_memory or search_memory or say when not to use this tool, but the whole-workspace export scope is unambiguous.

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

All Renor toolsInspect
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.

Resources