Skip to main content
Glama

remnus

by io.github.Ranork
OverviewDiscussionsAdmin

update_page

Idempotent

Update a page or database row. Only the fields you pass are changed — omit a field to leave it untouched. For rows, properties are merged into the existing values (not replaced), and title also updates the row's title property so the change shows up in table views.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNew title
pageIdYesThe workspace item ID or database row ID to update
contentNoNew markdown content
knowledgeNoOptional OKF-aligned knowledge metadata. Agent-authored knowledge remains draft/machine-confirmed until a Remnus user reviews the exact revision.
propertiesNoProperties to merge (for database rows)
recurrenceNoRepeat this database row on a schedule. Occurrences are created as real rows.
contextRunIdNoprepare_context contextRunId. Required for mutations when the workspace uses Strict context.
recurrenceScopeNoRequired when the row ALREADY repeats: "thisAndFollowing" leaves earlier cards untouched, "all" re-rhythms the whole series. Ask the user rather than guessing.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the updated page or row
updatedYesWhether the update was applied
recurrenceErrorNoSet when the rhythm change was refused — the row update itself still applied

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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"
+}
    • addedInput schema / properties / recurrenceScope
      Added value: +{
+  "description": "Required when the row ALREADY repeats: \"thisAndFollowing\" leaves earlier cards untouched, \"all\" re-rhythms the whole series. Ask the user rather than guessing.",
+  "enum": [
+    "thisAndFollowing",
+    "all"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / recurrenceError
      Added value: +{
+  "description": "Set when the rhythm change was refused — the row update itself still applied",
+  "type": "string"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds valuable behavioral context beyond annotations: partial update semantics ('only fields you pass are changed'), merge behavior for properties, and the side effect that title also updates the row's title property. It also discloses that recurrence creates real rows and that contextRunId is required for mutations in Strict context. This is strong behavioral disclosure that goes beyond the structured fields.

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 two sentences, front-loaded with the core purpose and the most important behavioral rule (partial updates). The second sentence adds essential merge semantics. It is concise and every sentence earns its place. Slightly more could be said about when not to use it, but the structure is efficient and readable.

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?

Given the tool's complexity (8 params, nested objects, output schema present), the description covers the critical behavioral aspects: partial updates, merge semantics, title side effect, recurrence row creation, and Strict context requirement. The output schema exists so return values need not be described. The only gap is not explicitly routing to bulk_update_pages for batch scenarios, but the description is complete enough for an agent to call this tool correctly in most cases.

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 description coverage is 100%, so the schema already documents all parameters. The description adds meaning beyond the schema by explaining the merge semantics for properties and the title side effect, which are not evident from the schema alone. It also clarifies the recurrence behavior ('Occurrences are created as real rows') and the contextRunId requirement. This exceeds the baseline 3 for full schema coverage.

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 updates a page or database row, and explicitly distinguishes the two target types. It also names the sibling tool it is not (create_page) implicitly by focusing on update semantics, and the title 'Update page' aligns with the description. The verb 'update' plus resource 'page or database row' is specific and unambiguous.

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 explains when to use this tool (to update a page or database row) and provides key usage context: partial updates, merge semantics for rows, and title behavior. It does not explicitly name alternatives like bulk_update_pages or create_page, but the context signals and sibling list make the distinction inferable. The description could be stronger by explicitly saying 'for bulk updates use bulk_update_pages' but the core usage guidance is clear.

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

All remnus 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