Skip to main content
Glama

AICTIONBOT™ Werkbank

Open a new Shared Table: one encrypted file for two sides (need, scope, offers, decision, open points)

open_table

KULIC Advisory, AICTIONBOT™ Workbench. Opens a new Shared Table: one file for two sides, for example procurement and the requesting department, or buyer and supplier. Six fields: need, scope of work, offers, decision, open points (can be ticked off) and notes. The content is encrypted with a key that only the table link carries (the part after #). Returns that link: whoever has it can read, write and delete the table in the browser (no account) or through this connector. Optionally adds first entries. The table expires 30 days after the last change. Pass only what the user wants to share with the other side. Needs sign-in: runs with an AICTIONBOT™ Werkbank licence; without a licence one check per connection every 30 days is free (sign in with “Connect without a licence”).

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": {
      "title": "<title>"
    },
    "name": "open_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesProject title, for example: Cleaning services from 2027.
authorNoName shown with the entries. Default: AICTIONBOT™ Connector.
entriesNoOptional first entries.
languageNoLanguage of the answer and of the link (German or English page). Default de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

With annotations only marking it as a non-read-only, non-destructive creation, the description adds substantial behavioral context: content is encrypted with a key carried only in the link fragment, the link grants read/write/delete in a browser without an account, and the table expires 30 days after the last change. The licence and free-check terms are also disclosed. None of this contradicts the annotations.

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 purpose is front-loaded and the encryption/expiry/licence details all earn their place. The branding prefix and trademark-laden licence sentence add some noise, but structure remains scannable.

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, and the description compensates by explaining exactly what is returned (the link) and what holding it enables. Encryption, expiry, privacy boundaries and authentication requirements cover everything an agent needs before calling it.

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 the baseline is 3. The description does add a little meaning by tying the six named fields to the entries' field enum and noting entries are optional, but title, author and language semantics are left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Opens a new Shared Table: one file for two sides', and enumerates the six fields the table contains. It is clearly distinguishable from read/change/delete table siblings by the act of creation, although it never names a sibling explicitly to route against.

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?

It gives useful content guidance ('Pass only what the user wants to share with the other side') and states the sign-in/licence prerequisite. However, it never says when to use this versus change_table or add_to_table, or that a table should only be opened once per engagement.

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.