remnus

update_database_schema

Destructive

Add or remove columns from a database schema. Removing columns is destructive (data loss) and requires confirm: true. The title column cannot be removed.

Input Schema

TableJSON Schema

Name	Required	Description
`confirm`	No	Required when removing columns. Set to true to confirm the destructive operation.
`addColumns`	No	Columns to add
`databaseId`	Yes	Database ID (from list_workspace or search)
`contextRunId`	No	prepare_context contextRunId. Required for mutations when the workspace uses Strict context.
`removeColumnIds`	No	Column IDs to remove (use get_database_schema to find IDs). Cannot remove the title column.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`schema`	Yes	The new column schema after the change
`updated`	Yes	Whether the schema was updated

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

First observedJun 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds valuable behavioral details beyond annotations: the requirement for confirm: true during removal, the data-loss warning, and the title column restriction. This helps the agent understand side effects and necessary confirmations.

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 concise: two sentences that front-load the purpose and immediately cover the critical destructive behavior and constraints. No wasted words; 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?

For a schema-modification tool, the description covers the essential aspects: purpose, destructive nature, confirm requirement, and a specific restriction. The output schema is present, so return values are presumably documented there. It could mention idempotency or the need for a contextRunId in strict mode, but those are secondary.

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 the schema fully documents all parameters. The description adds minimal extra semantics—it restates the add/remove purpose and mentions the confirm requirement, but doesn't provide syntax or format details beyond the schema. 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 clearly states the tool's function: 'Add or remove columns from a database schema.' This is specific, uses a clear verb and resource, and distinguishes it from sibling tools like create_database or update_database_view. The destructive nature is also highlighted.

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 provides clear context on when to use the tool (adding/removing columns) and includes important constraints like 'requires confirm: true' for removal and 'The title column cannot be removed.' However, it does not explicitly mention alternatives or when not to use this tool, though the specific scope makes it fairly clear.

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.