remnus

create_database

Create a new database with a custom schema. A "Title" text column is always prepended if not provided.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Database name
`schema`	No	Column definitions. Omit to use default schema (Title + Status).
`parentId`	No	Parent workspace item ID (omit for root)
`knowledge`	No	Optional OKF-aligned knowledge metadata. Agent-authored knowledge remains draft/machine-confirmed until a Remnus user reviews the exact revision.
`contextRunId`	No	prepare_context contextRunId. Required for mutations when the workspace uses Strict context.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Workspace item ID of the new database
`databaseId`	Yes	Database ID used by query/schema tools

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 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"
+}

First observedJun 26, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already communicate that this is a mutating operation (readOnlyHint=false). The description adds a non-obvious behavioral detail beyond that: a 'Title' text column is always prepended if not provided. This is exactly the kind of side effect an agent needs to know before constructing a schema.

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 short sentences with no filler. The core purpose is front-loaded in the first sentence, and the second sentence adds the one caveat worth surfacing. Everything present earns its place.

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?

For a mutating tool with nested parameters, the rich input schema and output schema carry much of the detail an agent needs. The description supplies the most surprising runtime behavior (Title prepending), though it leaves selection guidance against create_database_view and update_database_schema to the agent.

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

Parameters3/5

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

Schema description coverage is 100%, so all five parameters are already documented in the input schema. The description adds value only for the schema parameter via the Title-prepending behavior; it does not enrich the semantics of name, parentId, knowledge, or contextRunId. Baseline 3 is appropriate.

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 action ('Create') and resource ('a new database'), and further clarifies that it supports a custom schema. This clearly separates it from siblings like create_database_view and update_database_schema, which concern different operations and resources.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tools are named. The phrase 'Create a new database' implies this is for initial creation rather than updating a schema or creating a view, but the agent must infer that distinction from the tool name and siblings.

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.