Skip to main content
Glama

AICTIONBOT™ Werkbank

Who is responsible: from your own list of topics, people in charge, deputies and value limits, the answer to who to ask and who may sign, with a notice and the gaps

find_responsible
Read-onlyIdempotent

AICTIONBOT™ who is responsible by KULIC Advisory (tool 72). Takes your own list with one row per topic (topic, role or person in charge, deputy, value limit in euros, contact) and optionally a question and an amount. Returns the entries that match the question, who may sign the amount (the lowest limit that covers it), a notice sorted by topic, the signing ladder, and the gaps: two people in charge of the same topic and an amount above every limit (red), topics without a deputy and one person carrying more than 40 percent of the topics (yellow). Deterministic keyword matching, no AI, nothing stored. It only uses your list and invents no names. To check a full approval matrix against a people list use check_approval_matrix, for a RASCI matrix use check_rasci_matrix. 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": "find_responsible"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesOne row per topic: topic, responsible, deputy, limit (euros), contact. German column names work too (thema, zustaendig, vertretung, grenze, kontakt).
languageNoLanguage of the answer. Default de.
questionNoOptional: the question in plain words, for example who signs a framework contract.
amount_eurNoOptional: the amount in euros that needs a signature.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses that matching is deterministic keyword matching with no AI, that nothing is stored, and that names are never invented. It also states the licence prerequisite and the free-tier limit of one check per connection every 30 days. The only shortfall is that it does not describe response shape or size limits, so it stops just short of a 5.

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?

It is front-loaded with purpose, then alternatives, then the licence caveat, and every sentence carries information. It is dense and includes branding plus a fairly long licensing clause, which costs some tightness but not enough to undermine usability.

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?

With no output schema, the description carries the burden of describing returns, and it does: matching entries, the signing ladder, the sorted notice, and the specific red and yellow gap categories. Licence and privacy behavior are also covered, so an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds real meaning: rows are one per topic with the five fields, German column names are accepted, and the amount parameter resolves to the lowest limit that covers it. That lowest-limit signing logic is not derivable from the schema alone.

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 verb and resource: it takes a topic/responsible/deputy/limit list and returns matching entries, who may sign an amount, a notice, a signing ladder, and gaps. It explicitly distinguishes itself from check_approval_matrix and check_rasci_matrix, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names two alternatives with the exact condition that selects them: use check_approval_matrix for a full approval matrix against a people list, check_rasci_matrix for a RASCI matrix. Usage context (optional question and amount) is also spelled out, leaving nothing to inference.

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.