remnus

update_database_view

Idempotent

Rename a database view, change its icon, or patch fields within its existing config (filters, sorts, groupByCol, dateCol, cardProperties, etc — merged into the current config). The view's type (table/kanban/calendar) cannot be changed; create a new view instead. Use get_database_schema to find view ids and current config shape.

Input Schema

TableJSON Schema

Name	Required	Description
`icon`	No	Emoji, "lucide:Name", or image URL
`name`	No	New view name
`config`	No	Partial config fields to merge in, e.g. { "groupByCol": "col_abc123" } or { "filters": [...] }
`viewId`	Yes	View ID (from get_database_schema)
`iconColor`	No	Theme color for a lucide icon
`databaseId`	Yes	Database ID (from list_workspace or search)
`contextRunId`	No	prepare_context contextRunId. Required for mutations when the workspace uses Strict context.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`view`	Yes
`updated`	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.6/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, so the safety profile is covered. The description adds valuable behavioral context: config fields are merged into the existing config (not replaced), and the view type is immutable. This goes beyond what annotations provide, though it doesn't detail side effects like whether renaming affects references.

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?

Three sentences with no filler. The core action and merge behavior are front-loaded, the immutability constraint is stated clearly, and the pointer to get_database_schema is a useful final note. Every sentence 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?

The description is complete for a mutation tool with an output schema and full parameter documentation. It covers the key behavioral nuance (merge vs replace), the immutability constraint, and how to find required IDs. It doesn't mention potential errors or permission requirements, but given the annotations and schema coverage, this is a minor gap.

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 by explaining the merge semantics for config and explicitly listing example fields (filters, sorts, groupByCol, dateCol, cardProperties). It also clarifies that icon can be an emoji, lucide:Name, or image URL, which is useful beyond the raw schema.

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 verb ('Rename', 'change', 'patch') and resource ('database view'), and explicitly distinguishes itself from creating a new view when the type needs to change. It also names the sibling tool get_database_schema for finding view IDs, which helps an agent understand exactly what this tool operates on.

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?

The description explicitly says when to use this tool (rename, change icon, patch config fields) and when not to use it (cannot change view type; create a new view instead). It also points to get_database_schema for finding view IDs and current config shape, which is clear guidance for the correct invocation context.

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.