Skip to main content
Glama

AICTIONBOT™ Werkbank

Add entries to a Shared Table or tick off open points

add_to_table

KULIC Advisory, AICTIONBOT™ Workbench. Adds entries to a Shared Table (need, scope of work, offers, decision, open points, notes) and can tick off or reopen open points by their id from read_table. Needs the full table link including the part after #. The other side sees the change in the browser within a few seconds. Changes by both sides are merged; nothing is overwritten. Only add what the user asked for.

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": "add_to_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
doneNoIds of open points to tick off.
linkYesThe full table link including the part after #.
authorNoName shown with the entries. Default: AICTIONBOT™ Connector.
reopenNoIds of open points to open again.
entriesNo
languageNoLanguage of the answer. Default de.

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?

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the other side sees changes in the browser within seconds, and concurrent edits by both sides are merged so nothing is overwritten. It does not mention failure modes, what happens if an id is invalid, or the size limits already present in the schema, so 5 is not warranted.

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 core capability and its prerequisite are front-loaded in the first two sentences, and the merge/latency caveat follows logically. The leading "KULIC Advisory, AICTIONBOT™ Workbench" branding is filler that does not help an agent decide anything, which keeps it from a 5.

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 a mutating shared-state tool with no output schema, the description supplies the essential missing context: link format requirement, real-time visibility, non-destructive merge semantics, and a scope discipline instruction. It leaves return-value expectations and per-entry limits to the schema, which is acceptable.

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?

With 83% schema description coverage, the schema already documents link, done, reopen, author and language. The description's main addition is the provenance of the id arrays (read_table), which is useful semantics beyond the schema; the link format note largely restates the schema's own description. 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?

Uses a specific verb and resource (adds entries to a Shared Table) and enumerates the concrete fields (need, scope of work, offers, decision, open points, notes), plus a second capability (tick off / reopen open points). It also implicitly distinguishes itself from read_table, which it names as the source of the point ids.

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?

"Can tick off or reopen open points by their id from read_table" tells the agent where to obtain ids and that this tool is the write counterpart of read_table. The prerequisite ("needs the full table link including the part after #") and the caution "Only add what the user asked for" give clear operating context. It stops short of explicit when-not-to-use guidance versus open_table or other write paths, so it is a 4 rather than a 5.

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.