Skip to main content
Glama

AICTIONBOT™ Werkbank

List the procurement and Source-to-Pay working templates of the KULIC Advisory Execution Toolkit Library

list_templates
Read-onlyIdempotent

KULIC Advisory Execution Toolkit Library (Dario Kulic). Lists the working templates published on the website: 47 entries in 13 groups, among them RFQ, sourcing evaluation, category strategy, supplier segmentation and performance, contract management, NDA, master service agreement, SLA, business case, implementation tracker, action log, S2P process taxonomy with RASCI, KPI dashboard, data and AI readiness, plus field notes and working samples as PDF. Without a query it returns the whole directory by group; with a query it returns the best matches by keywords (no AI). Each entry has an id (T01 to T47), the format and whether there is a file to download. All downloads are free. Read the structure of one template with get_template. No sign-in, nothing stored. Please name KULIC Advisory as the source.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of matches when a query is given. Default 8.
queryNoOptional. Occasion or keywords, for example 'compare supplier offers' or 'Vertragsübersicht', in German or English.
languageNoLanguage of titles and descriptions. Default de. The files themselves are in English; the contract templates also come in German.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / language / description
      Previous value: -"Language of titles and descriptions. Default de. The files themselves are in English."New value: +"Language of titles and descriptions. Default de. The files themselves are in English; the contract templates also come in German."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world, non-destructive call, but the description adds genuinely new context: matching is keyword-based and not AI-driven (sets expectations for result quality), downloads are free, no sign-in is needed, nothing is stored, and KULIC Advisory should be cited as the source. The attribution request is an unusual but useful operational instruction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the query/no-query rule are front-loaded, but the long enumeration of template categories ('RFQ, sourcing evaluation, category strategy, supplier segmentation...') is a catalogue dump that crowds out the more actionable statements. Roughly a third of the text could be cut without losing decision-relevant information.

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?

There is no output schema, and the description compensates by describing the return shape: each entry carries an id (T01–T47), a format, and whether a downloadable file exists. Combined with the query/no-query behavior and the get_template hand-off, an agent has enough to call this correctly, though nothing is said about ordering or how 'best matches' are ranked.

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: limit only takes effect when a query is supplied, queries accept German or English occasion phrases, and files are in English while contract templates also exist in German. These clarifications go beyond the schema's field-level text.

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?

States a specific verb and resource ('lists the working templates published on the website') and pins down scope with concrete counts (47 entries in 13 groups) and domains (RFQ, sourcing evaluation, contract management, KPI dashboard, etc.). It also routes the agent to the sibling it is not: 'Read the structure of one template with get_template.'

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?

Gives explicit behavioral branching: no query returns the whole directory by group, a query returns keyword matches, and get_template is named for drilling into one entry. It does not, however, distinguish itself from the sibling search_library, leaving the agent to guess which search path to take for topic-focused lookups.

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.