Skip to main content
Glama

AICTIONBOT™ Werkbank

Change a Shared Table: edit or remove entries, connect cards on the board, rename

change_table
Destructive

KULIC Advisory, AICTIONBOT™ Workbench. Changes a Shared Table from its full link (including the part after #): edit the text of entries or remove them by their id from read_table, draw or remove lines between two cards on the free board, and rename the table. A removed entry stays removed for both sides. Only change what the user asked for; the other side sees the change in the browser within a few seconds.

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>"
    },
    "name": "change_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
editNoEntries to rewrite, by id.
linkYesThe full table link including the part after #.
titleNoNew title of the table.
authorNoName shown with new lines. Default: AICTIONBOT™ Connector.
removeNoIds of entries to remove.
connectNoLines to draw between two entries on the free board.
languageNoLanguage of the answer. Default de.
disconnectNoLines to remove, by their two entries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that removals are permanent for both sides, that the other party sees changes in the browser within seconds, and that the link must include the fragment after '#'. It leaves idempotency/repeat-call behavior and any permission requirements unstated, which matters given idempotentHint=false and destructiveHint=true.

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?

Operations are front-loaded and the sentence structure is efficient, with the practical warnings kept short. The branding preamble ('KULIC Advisory, AICTIONBOT™ Workbench') contributes nothing to tool selection and could be dropped.

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 an eight-parameter mutation tool with no output schema, the description covers all operation groups, the destructive cross-user effect, and propagation timing. It stops short of error behavior (missing ids, partial failure) and concurrency, which an agent would otherwise have to discover empirically.

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 parameter meaning is already carried by the schema. The description adds one non-trivial hint — that entry ids come from read_table — but does not explain how edit/remove/connect/disconnect interact in a single call or what happens with unknown ids, so 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?

States a specific verb and resource and then enumerates the three concrete operations (edit entry text, remove entries, draw/remove board lines, rename) so the agent knows exactly what the tool can do. It also distinguishes itself from read_table by noting that entry ids come from there, making sibling selection unambiguous.

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?

Gives real usage constraint: 'Only change what the user asked for', which scopes the agent away from speculative edits, and points at read_table as the source of ids. It does not explicitly contrast with add_to_table or delete_table (adding vs removing whole tables), so an agent must infer those boundaries.

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.