Skip to main content
Glama

AICTIONBOT™ Werkbank

Delete a Shared Table for both sides

delete_table
DestructiveIdempotent

KULIC Advisory, AICTIONBOT™ Workbench. Deletes a Shared Table at once, for everyone who has the link. This cannot be undone. Use it only when the user explicitly asks to delete this table, and pass confirm: true. Without deletion a table expires 30 days after the last change anyway.

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": {
      "link": "<link>",
      "confirm": "<confirm>"
    },
    "name": "delete_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe full table link including the part after #.
confirmYesMust be true: the user asked to delete this table.
languageNoLanguage of the answer. Default de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description goes beyond them by stating the change is global to everyone holding the link and cannot be undone, plus a real behavioral fact an agent would otherwise miss: untouched tables expire 30 days after the last change anyway. That expiry note materially changes the cost/benefit of calling the tool and is exactly the kind of context structured fields cannot carry.

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?

The irreversible scope and the usage restriction are front-loaded in tight sentences, which is the right ordering for a destructive tool. The opening product/branding preamble ('KULIC Advisory, AICTIONBOT™ Workbench') earns no place in a tool description and is the only real waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema to explain, no nested objects, and all three parameters are schema-documented, so the description only needs to cover risk and eligibility. It does that: irreversible, global, requires explicit user intent, with a fallback expiry behavior noted. Nothing an agent needs in order to call this correctly is missing.

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 coverage is 100%, so link, confirm, and the language enum are already fully documented, and the description's 'pass confirm: true' largely restates the schema's own note. It adds the motive for confirm (the user asked) but no new syntax, format, or default information, 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?

The description names a specific verb and resource ('Deletes a Shared Table') and immediately scopes the blast radius ('at once, for everyone who has the link'), which implicitly separates it from per-user editing siblings such as change_table or add_to_table. An agent can identify this as the global, irreversible delete without opening the schema.

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 gives a clear gating condition: use it only when the user explicitly asks to delete this table, and it pairs that with the 'confirm: true' requirement. It stops short of naming a concrete alternative (e.g., change_table for edits), so it is strong context rather than a full when/when-not/alternatives routing statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.