WiseGrid MCP

delete_row

Delete a row and all its child rows from a WiseGrid sheet. Requires explicit confirmation; inspect the subtree first to avoid data loss.

Instructions

Delete a row AND ALL OF ITS CHILD ROWS. Destructive and not undoable through this API.

Requires confirm=True. Read the row and its children first so you know what the subtree contains — a parent row can carry descendants that are not obvious from the row itself.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sheet_id": "<sheet_id>",
      "row_id": "<row_id>"
    },
    "name": "delete_row"
  }
}

Input Schema

Name	Required	Description	Default
`row_id`	Yes
`confirm`	No
`sheet_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the destructive and irreversible nature, the cascade delete behavior, the confirm requirement, and the subtlety that hidden descendants may exist. This is thorough and goes beyond what typical mutation descriptions offer.

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 two sentences, each earning its place: the first states the core action, the second provides the critical warning and prerequisite. It is concise, well-structured, and front-loaded with the most important information.

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 fully covers the destructive scope, prerequisite reading, and the confirm requirement. It doesn't describe error handling or return values, but the presence of an output schema reduces that burden, and the core behavior is thoroughly explained for a tool of this complexity.

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 0%, so the description must compensate. It clarifies the confirm parameter's requirement and purpose, but does not explicitly explain sheet_id or row_id. However, their names strongly imply their roles (sheet and row identifiers), providing partial compensation for the schema gap.

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 deletes a row and all its child rows, using the specific verb 'delete' and clearly naming the resource. The all-caps emphasis on child rows distinguishes it from a simple row deletion and from sibling tools like update_row.

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 warns that the operation is destructive and not undoable, requires confirm=True, and advises reading the row and children first. It doesn't name an alternative tool, but few alternatives exist for a delete operation; the preconditions and safety guidance provide strong usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server