remnus

create_page

Create a new standalone page (use parentId to nest it) or a database row (use databaseId). For rows, properties keys may be column names or ids (matched case-insensitively); title is always mirrored into the row's own title property.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Page title
`content`	No	Initial markdown content
`parentId`	No	Parent workspace item ID (for standalone pages)
`knowledge`	No	Optional OKF-aligned knowledge metadata. Agent-authored knowledge remains draft/machine-confirmed until a Remnus user reviews the exact revision.
`databaseId`	No	Database ID (creates a database row instead of a page)
`properties`	No	Initial properties (for database rows)
`recurrence`	No	Repeat this database row on a schedule. Occurrences are created as real rows.
`contextRunId`	No	prepare_context contextRunId. Required for mutations when the workspace uses Strict context.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	ID of the created page or row
`type`	Yes	What was created (page \| db-row)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 10, 2026

addedInput schema / properties / contextRunId

Added value: +{
+  "description": "prepare_context contextRunId. Required for mutations when the workspace uses Strict context.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

addedInput schema / properties / knowledge

Added value: +{
+  "description": "Optional OKF-aligned knowledge metadata. Agent-authored knowledge remains draft/machine-confirmed until a Remnus user reviews the exact revision.",
+  "properties": {
+    "conceptType": {
+      "maxLength": 120,
+      "type": "string"
+    },
+    "description": {
+      "maxLength": 1000,
+      "type": "string"
+    },
+    "sources": {
+      "items": {
+        "properties": {
+          "resource": {
+            "maxLength": 2000,
+            "type": "string"
+          },
+          "title": {
+            "maxLength": 300,
+            "type": "string"
+          }
+        },
+        "required": [
+          "resource"
+        ],
+        "type": "object"
+      },
+      "maxItems": 20,
+      "type": "array"
+    },
+    "staleAfter": {
+      "maxLength": 40,
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "draft",
+        "stable",
+        "deprecated"
+      ],
+      "type": "string"
+    },
+    "tags": {
+      "items": {
+        "maxLength": 80,
+        "type": "string"
+      },
+      "maxItems": 30,
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / recurrence

Added value: +{
+  "description": "Repeat this database row on a schedule. Occurrences are created as real rows.",
+  "properties": {
+    "byMonthDay": {
+      "maximum": 31,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "bySetPos": {
+      "anyOf": [
+        {
+          "const": -1,
+          "type": "number"
+        },
+        {
+          "const": 1,
+          "type": "number"
+        },
+        {
+          "const": 2,
+          "type": "number"
+        },
+        {
+          "const": 3,
+          "type": "number"
+        },
+        {
+          "const": 4,
+          "type": "number"
+        }
+      ],
+      "description": "-1 = last"
+    },
+    "byWeekday": {
+      "items": {
+        "enum": [
+          "MO",
+          "TU",
+          "WE",
+          "TH",
+          "FR",
+          "SA",
+          "SU"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "count": {
+      "maximum": 500,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "dateColumn": {
+      "description": "Column id or name; defaults to the first date column",
+      "type": "string"
+    },
+    "freq": {
+      "enum": [
+        "daily",
+        "weekly",
+        "monthly",
+        "yearly"
+      ],
+      "type": "string"
+    },
+    "interval": {
+      "description": "1 = every, 2 = every other",
+      "maximum": 99,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "monthlyMode": {
+      "enum": [
+        "dayOfMonth",
+        "nthWeekday",
+        "lastDay"
+      ],
+      "type": "string"
+    },
+    "until": {
+      "description": "YYYY-MM-DD, inclusive",
+      "type": "string"
+    }
+  },
+  "required": [
+    "freq"
+  ],
+  "type": "object"
+}

First observedJun 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses useful behaviors beyond the annotations: properties keys can be column names or ids and are matched case-insensitively, and title is always mirrored into the row's own title property. It adds meaningful behavioral nuance without contradicting 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?

Two tightly written sentences with no filler. The core distinction between page and row creation is front-loaded, and the additional row-specific behavior is introduced in a compact second sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has eight parameters and nested objects, but the input schema covers every parameter and an output schema is present. The description adds the key conceptual distinction between pages and rows. It does not mention recurrence or contextRunId, but both are well-documented in the schema.

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?

With 100% schema description coverage, the baseline is 3, but the description adds cross-parameter semantics by explaining the relationship between parentId/databaseId modes and the properties key-matching behavior. This goes beyond individual parameter descriptions and helps agents construct valid calls.

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 uses a specific verb ('Create') and resource ('standalone page' or 'database row') and immediately clarifies the two distinct creation modes via parentId and databaseId. This clearly differentiates the tool from create_database and update_page, which operate on different resources.

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 context for when to use this tool: creating a new page or database row, with explicit direction on how to choose between parentId and databaseId. It does not explicitly name alternatives or state when not to use it, but the creation-focused guidance is solid.

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.