Skip to main content
Glama

AICTIONBOT™ Werkbank

Fill a table section of an Excel template or the placeholders of a Word template with the user's own values

fill_template
Read-onlyIdempotent

KULIC Advisory Execution Toolkit Library. Purely mechanical, no AI and no calculation. For an Excel template: pass the id, the section (number or title from get_template) and rows as objects keyed by column name. Returns the rows in the template's column order, the exact cell for every value (for example F10) so the values can be written into the downloaded file, and notes: columns the file calculates are left out, unknown fields and values outside a dropdown are named, rows beyond the prepared rows are listed without a cell. For a Word template (master service agreement, NDA, SLA): pass the id and values keyed by placeholder text without brackets, for example { "Party A": "Muster GmbH" }; returns the text with these placeholders replaced and the list of placeholders still open. Nothing is stored. The result is a working draft, not legal advice. 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": {
      "id": "<id>"
    },
    "name": "fill_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the template, T01 to T44.
rowsNoExcel templates: one object per row, keyed by column name as shown by get_template.
sheetNoExcel templates with several sheets: name of the sheet, if the section number exists on more than one.
valuesNoWord templates: placeholder text without brackets as key, replacement as value. A key may end with #2, #3 to address the second, third occurrence of a placeholder that appears several times.
sectionNoExcel templates: number or title of the table section as shown by get_template, for example '2' or 'COMMERCIAL RESPONSE TABLE'.
languageNoLanguage of the notes. 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?

Goes well beyond the readOnly/idempotent annotations by describing exactly what comes back: rows in template column order, the precise target cell (e.g., F10) per value, calculated columns omitted, unknown fields and out-of-dropdown values flagged, overflow rows listed without a cell, and still-open placeholders in Word mode. It also discloses that nothing is stored and that output is a working draft, not legal advice.

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?

Front-loaded and organized by mode, with the Excel branch first and the Word branch second, which matches the call pattern. It is dense but nearly every clause carries operational meaning; the toolkit branding opener and the length of the trailing licence/legal sentence are the main slack.

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?

Complete enough for a six-parameter tool with no output schema: return payload, cell mapping, notes, and side-effect profile are all covered. The one soft spot is how an agent determines whether a given template id is Excel or Word before choosing between rows and values, which is left implicit.

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 every parameter is already documented in the schema, including the #2/#3 occurrence convention. The description reinforces the keying model (column names for rows, bracket-free placeholder text for values) but adds little semantics the schema does not already carry.

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 names the exact verb and resource for both modes: passing a section plus rows into an Excel template table, and placeholder values into a Word template. It also names get_template as the source of section numbers and column names, so an agent can tell this tool apart from the discovery siblings without opening a schema.

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?

Clear conditional guidance: use 'id + section + rows' for Excel templates, 'id + values' for Word templates, with a concrete placeholder example. Prerequisites (licence/sign-in) are stated. What is missing is any explicit exclusion or named alternative for when not to use it, e.g., when a section does not exist or when a table should be edited rather than filled.

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.