Skip to main content
Glama
Sign In

Tokenrip

by com.tokenrip
OverviewDiscussionsAdmin

Delete table rows

table_delete_rows
DestructiveIdempotent

Delete up to 1000 rows by their own ids (rowIds), all of one table (rows of two tables are INVALID_INPUT). An id that names no row you can read is skipped. Workspace tables need why; expectedRevisions is optional and refuses (CONFLICT) a row that changed since.

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": {
      "rowIds": "<rowIds>"
    },
    "name": "table_delete_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyNoRequired for workspace items: one sentence on what the person is trying to accomplish, in their terms, not a description of this edit. Every workspace write takes one; sessions and summaries record themselves from it. At most 300 characters.
rowIdsYesAt most 1000 row ids, all of one table. An id that names no row is skipped.
expectedRevisionsNoOptional, per row (keyed by an id of rowIds): refuse (CONFLICT) if that row changed since this revision or no longer exists.

Output Schema

NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description earns credit beyond that by disclosing skip semantics for unreadable/absent ids and the exact CONFLICT trigger for stale revisions, which are not in the annotations. It omits the biggest remaining question for a destructive tool: whether rows are recoverable (trash_restore exists as a sibling) or permanently gone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences with the limit and single-table rule front-loaded, no filler. Slightly telegraphic phrasing ('Workspace tables need why') costs a bit of readability but not much space.

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?

Output schema is present so return values need no explanation, and the description covers the batch limit, single-table rule, missing-id skipping, workspace `why` prerequisite and revision conflicts. The notable gap is recoverability/permanence and any partial-success semantics for a destructive batch delete.

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 all three parameters are already documented in structured form. The description summarizes rowIds, why and expectedRevisions but adds little syntax or meaning the schema does not already carry, so the baseline 3 applies.

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?

Specific verb (delete) plus resource (rows) plus a hard scope constraint: up to 1000 ids, all belonging to one table, with two-table input declared invalid. An agent can immediately separate this from table_append_rows and table_update_row without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real preconditions – workspace tables require `why`, and `expectedRevisions` is optional with described conflict behavior – but never routes the agent between alternatives, e.g. when to prefer a single-row update, or whether a deleted row can be brought back with trash_restore. Usage is implied by the constraints rather than stated as when/when-not.

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

All Tokenrip 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