Skip to main content
Glama

AICTIONBOT™ Werkbank

Data X-ray for any list: fill rate per column, formats (email, IBAN, VAT ID, date, number), duplicates, spelling variants, outliers, personal data

audit_list
Read-onlyIdempotent

AICTIONBOT™ data X-ray by KULIC Advisory, built on the Execution Toolkit template T24 (self data audit). Takes any list (one row per record) and returns per column the fill rate, the detected type (email, IBAN with checksum, VAT ID, date, phone, number, text), invalid values with examples, spelling variants and stray spaces, numeric outliers and whether it probably holds personal data; for the list the key column with its duplicates, exact duplicate rows and a score from 1 to 5 for completeness, validity, uniqueness and consistency (below 3 means clean up before automation or AI). For vendor lists check_vendor_master adds IBAN, VAT ID and risk signals. Deterministic, no AI, nothing stored. 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": {
      "rows": "<rows>"
    },
    "name": "audit_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoColumn that should be unique (e.g. supplier number). Default: detected.
rowsYesThe list, one object per row, column names as keys.
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 establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds material behavioral context beyond those annotations: deterministic processing, no AI, nothing stored, and a sign-in/licence requirement with a limited free tier. This is exactly the kind of operational context an agent needs before invoking the tool.

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 description front-loads the core purpose and packs useful detail into a single paragraph, but the opening branding and template reference dilute the first sentence. It is appropriately detailed for a complex audit tool, though the semicolon-heavy structure makes it less scannable than it could be.

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?

Although there is no output schema, the description explains the return values in detail: per-column fill rate, detected type, invalid values, spelling variants, outliers, personal-data likelihood, key-column duplicates, exact duplicate rows, and four 1–5 quality scores. It also covers authentication and licence limits, so an agent has enough information to call the tool correctly and understand what it will receive.

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 the input schema already documents all three parameters, including their defaults and the key-column meaning. The description adds minor context by saying the input is one row per record and that the key column is checked for duplicates, but it does not explain the language parameter or add syntax beyond the schema. 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?

The description states a specific resource and operation: a data X-ray of any list, returning per-column fill rate, detected type, invalid values, variants, outliers, and quality scores. It is clearly distinguishable from sibling tools and explicitly points vendor-list users to check_vendor_master for additional IBAN, VAT ID, and risk signals.

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?

The description gives clear usage context: it is for auditing any list before automation or AI, with a score below 3 meaning cleanup is needed. It names check_vendor_master as an alternative for vendor lists, but it does not provide broader when-not-to-use guidance or compare against other list-processing siblings such as find_in_list or fill_template.

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.