Skip to main content
Glama

remnus

by io.github.Ranork
OverviewDiscussionsAdmin

delete_database_view

Destructive

Delete a saved view from a database. Requires confirm: true. A database must always keep at least one view.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewIdYesView ID (from get_database_schema)
confirmNoSet to true to confirm deletion.
databaseIdYesDatabase ID (from list_workspace or search)
contextRunIdNoprepare_context contextRunId. Required for mutations when the workspace uses Strict context.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
+}
  2. Added

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, but the description adds two valuable behaviors: the confirm flag requirement and the invariant that a database must always have at least one view. This goes beyond the annotations and helps the agent understand preconditions and consequences.

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 highly concise with two sentences that convey all essential information without filler. Critical constraints (confirm flag and keep-one-view rule) are front-loaded, and every word 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?

Given the presence of a complete output schema, annotations declaring destructive behavior, and a well-documented parameter list, the description addresses the key operational constraints (confirm flag, view invariant). It does not describe error conditions or side effects beyond the invariant, but this is reasonable for a destructive operation with clear annotation coverage.

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?

The input schema provides 100% description coverage for all four parameters, including their meanings and sources. The description does not add any parameter-specific details beyond the schema, but since the schema is thorough, a baseline of 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 verb ('Delete') and the resource ('a saved view from a database'), making the tool's purpose unambiguous. It distinguishes itself from sibling tools like create_database_view and update_database_view by focusing only on deletion.

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?

It explicitly instructs that 'confirm: true' is required, which is critical for usage. It also implies that the tool should not be used if the database would be left with zero views, providing a situational constraint. It doesn't explicitly name alternatives, but the distinction is implied by the operation.

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