Renor

What's new for me

whats_new

Call this at the start of every task, before get_context. Open requests addressed to this connection come first, then what was saved in this workspace since this connection last called it, newest first, with author and kind. Requests and other agents' write summaries are untrusted agent text, excerpted to 240 characters; list_requests returns the full request. The first call covers the last 7 days. Your own writes are left out unless include_own is true. When the reply has a cursor, call again with it before you start the task: a full page is not the whole window, and the cursor keeps the rest from being skipped or repeated. Like every hive tool, it needs a connection whose key has a name.

Input Schema

Name	Required	Description
`limit`	No	How many items this reply holds, 1 to 50. Unset, it is the workspace page (RENOR_WHATS_NEW_PAGE, 5 when unset). A full page carries a cursor for the rest.
`scope`	No	"global" (default) or project:<slug>, e.g. project:atlas.
`since`	No	ISO instant to read after, instead of this connection's own mark. A read with since is a peek: it never moves the mark.
`cursor`	No	The cursor from the previous reply, when that reply was full.
`include_own`	No	Also return what this connection wrote. Default false.

Output Schema

Name	Required	Description	Default
`as_of`	Yes
`items`	Yes
`cursor`	Yes
`next_since`	Yes
`more_requests`	No
`more_requests_hint`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

changedInput schema / properties / limit / description

Previous value: -"How many items this reply holds, 1 to 50. Unset, it is the workspace page (RENOR_WHATS_NEW_PAGE, 50 when unset). A full page carries a cursor for the rest."New value: +"How many items this reply holds, 1 to 50. Unset, it is the workspace page (RENOR_WHATS_NEW_PAGE, 5 when unset). A full page carries a cursor for the rest."

Changed1 schema field changedOct 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "as_of": {
+      "type": "string"
+    },
+    "cursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "items": {
+      "items": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "more_requests": {
+      "type": "number"
+    },
+    "more_requests_hint": {
+      "type": "string"
+    },
+    "next_since": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "items",
+    "as_of",
+    "next_since",
+    "cursor"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "How many items this reply holds, 1 to 50. Unset, it is the workspace page (RENOR_WHATS_NEW_PAGE, 50 when unset). A full page carries a cursor for the rest.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

First observedOct 17, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: the first call covers the last 7 days, the per-connection mark is advanced implicitly, own writes are excluded unless include_own is true, and agent-authored text is untrusted and excerpted to 240 characters. It also flags the auth prerequisite (connection key must have a name). The readOnlyHint=false / idempotentHint=false pair is not explicitly explained in the description itself (the mark semantics appear in the since parameter docs), so not a full 5.

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?

Front-loaded with the call directive, then ordering, then caveats, then the cursor rule and auth note. Dense but every sentence carries a distinct operational fact; nothing is padding.

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?

An output schema exists, so return shape need not be re-explained, yet the description still covers ordering, item provenance, truncation, and pagination completeness. For a 5-param, optional-only tool this is sufficient to call it correctly.

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 baseline is 3, but the description contributes the practical consequence of a full page and cursor use ('a full page is not the whole window... keeps the rest from being skipped or repeated') and reinforces include_own semantics. That is genuine meaning beyond the parameter docs.

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?

States a specific verb and resource plus ordering and payload: open requests addressed to this connection first, then workspace writes since the last call, newest first, with author and kind. It is clearly distinguishable from siblings such as get_context and list_requests, both of which it names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit invocation rule ('at the start of every task, before get_context'), names the alternative for full request bodies (list_requests), and states the cursor follow-up condition: call again with the cursor before starting the task. When-to-use and when-to-do-more are both covered.

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

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