remnus

create_database_view

Add a new saved view (table, kanban, or calendar) to a database. Kanban groups by a select/status column (auto-picks one if omitted); calendar places cards by a date/datetime column (auto-picks one if omitted). Use get_database_schema first to see column ids/names.

Input Schema

TableJSON Schema

Name	Required	Description
`icon`	No	Emoji, "lucide:Name", or image URL for the view tab
`name`	Yes	Name for the new view (e.g. "By Assignee")
`type`	Yes	View type
`dateCol`	No	Calendar only: date/datetime column id or name to place cards on. Auto-picks the first date/datetime column if omitted.
`iconColor`	No	Theme color for a lucide icon
`databaseId`	Yes	Database ID (from list_workspace or search)
`groupByCol`	No	Kanban only: select/status column id or name to group by. Auto-picks the first status/select column if omitted.
`contextRunId`	No	prepare_context contextRunId. Required for mutations when the workspace uses Strict context.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`view`	Yes
`created`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field 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"
+}

AddedJul 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The description aligns with annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) by presenting a mutation. It adds some behavioral context, such as auto-picking a select/status column for kanban and a date/datetime column for calendar, but much of this repeats the schema's own property descriptions. It does not disclose failure modes or side effects beyond the annotations already conveying the safety profile.

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?

The description is three sentences with no filler. The core action is front-loaded, and the kanban/calendar nuances and prerequisite are packed into the following two sentences without redundancy.

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 that the schema carries detailed parameter documentation and an output schema is present, the description covers what an agent needs most: the prerequisite schema lookup and the ambiguous auto-pick behavior. It could be slightly more complete with an explicit 'create vs update' routing note, but the sibling names largely cover that.

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% and the property descriptions already document groupByCol, dateCol, and type in detail. The description nevertheless adds practical meaning by connecting parameter choice to view behavior and by telling the agent to call get_database_schema to resolve valid column ids/names, which directly helps fill databaseId and the column parameters.

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 opens with a precise operation: 'Add a new saved view (table, kanban, or calendar) to a database.' It names the resource, the action, and the supported variants, making it immediately distinguishable from siblings like create_database, create_page, and update_database_view.

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 gives a clear, actionable precondition: 'Use get_database_schema first to see column ids/names.' It also explains when the optional kanban/calendar columns are needed and how auto-picking behaves. However, it does not explicitly contrast create with update_database_view or state when not to use this tool, so it falls short of a 5.

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.