Skip to main content
Glama

AICTIONBOT™ Werkbank

Read one template of the Execution Toolkit Library: what it is for, its structure and the download link

get_template
Read-onlyIdempotent

KULIC Advisory Execution Toolkit Library. Returns one template by its id (T01 to T44) from list_templates: what it is for and for whom, the download link and, for Excel templates, the structure read from the file: sheets, sections, the columns of each table, which columns the file calculates itself, the dropdown values and the first cell of each table. For the three Word templates (master service agreement, NDA, SLA) it returns the full text with the placeholders in square brackets. PDF entries come with description and link only. The files are in English and are working templates, not legal or tax advice. Fill a table or a Word template with fill_template. No AI, no sign-in, nothing stored.

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": "get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the template, T01 to T44, from list_templates.
languageNoLanguage of the description. Default de. Structure and text stay in English as in the file.

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?

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description still adds substantive behavior: what is returned differs by file type, Excel structure is read from the file itself (sheets, sections, columns, calculated columns, dropdown values, first cell), Word files return full text with bracketed placeholders, PDFs return description and link only. It also discloses language handling, the 'working template, not legal or tax advice' caveat, and that nothing is stored and no sign-in or AI is involved.

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 with the core action and identifier range, then the per-format return detail, then the routing sentence and caveats. Dense but every clause carries information; the one long middle sentence could be split into a short list without losing content.

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?

With no output schema, the description carries the return-value burden and does so per format, which is exactly what an agent needs. Minor gap: no guidance on invalid or out-of-range ids (e.g. T45, or a Word template queried with a language choice), so error expectations remain unstated for a read call.

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 both parameters are already documented, and the description's 'T01 to T44 from list_templates' largely restates the id field's schema text. The language parameter is not discussed in the description at all; a note that only the description is translated while structure/text stay English (which the schema does say) would have added value.

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 ('Returns one template by its id (T01 to T44)') and enumerates the payload per format: purpose/audience, download link, Excel structure details, Word full text, PDF description-and-link-only. An agent can distinguish it from list_templates (enumeration) and fill_template (writing) without opening any 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?

Explicitly routes discovery to list_templates ('by its id ... from list_templates') and downstream authoring to fill_template ('Fill a table or a Word template with fill_template'). It gives clear context but does not state exclusions, e.g. that it should not be used to browse the catalog or to search by topic (search_library).

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.