Skip to main content
Glama

AICTIONBOT™ Werkbank

Find a document number, order number, supplier number, name or keyword in a list and return the matching rows

find_in_list
Read-onlyIdempotent

AICTIONBOT™ Status Answer by KULIC Advisory. Searches a list the user provides, for example open items, open purchase orders or a supplier list, for a document number, order number, supplier number, name or keyword and returns the matching rows with their column names. Number spellings are normalised: RE-01042, re 1042 and 1042 are the same number, and an exact number wins over partial hits. All columns are searched. Use it to answer where an invoice or an order stands. 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": {
      "query": "<query>"
    },
    "name": "find_in_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNoAlternative to rows: the list as CSV or tab-separated text. The first line is the header.
rowsNoThe list as rows: one object per row, column name to value.
limitNoMaximum number of rows returned. Default 10.
queryYesWhat to look for: a number in any spelling, a name or a keyword.
languageNoLanguage of the answer. Default de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses matching behavior: number spellings are normalised (RE-01042, re 1042 and 1042 are the same), an exact number wins over partial hits, and all columns are searched. It also discloses that it is deterministic, stores nothing, and requires a licence sign-in with a stated free-tier limit, which is exactly the kind of auth constraint annotations cannot carry.

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 behavior-critical facts are front-loaded after a short brand line, and the normalization rule plus the matching precedence are stated in one dense sentence. The trailing licence sentence is long and mixes auth with marketing, but the substantive sentences all carry weight.

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?

For a five-parameter, read-only lookup with no output schema and full annotation coverage, the definition supplies everything an agent needs: what input forms are searched, how matching works, what comes back (matching rows with their column names), and what auth is required. Nothing material about the call is left to inference.

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, and the description still adds meaning to the central 'query' parameter by explaining that spellings are normalised and exact matches outrank partial ones. It leaves the csv-versus-rows choice and the limit/language defaults entirely 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?

States a specific verb and resource: it searches a user-supplied list (open items, purchase orders, supplier list) for a document number, order number, supplier number, name or keyword and returns matching rows. The scope of 'a list the user provides' is distinctive enough to separate it from most siblings, though no sibling is named as an alternative.

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?

Explicitly says to use it 'to answer where an invoice or an order stands' and gives concrete list examples, so the when-to-use condition is clear. It offers no when-not guidance and names no alternative tool, so the routing instruction is incomplete rather than ambiguous.

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.