Skip to main content
Glama

legal_put_generator

Toggle document modules and options, regenerate the chosen legal document, and return the updated generator state.

Instructions

Tick or untick modules and options, then regenerate the document (the Datenschutz tab over the API). Merges into the stored selection; unknown module or option keys are refused (400). Needs the library imported (409), and for datenschutz the required Impressum facts filled (409). Returns the new state as legal_get_generator does. Sections tied to a switch (Einwilligungsnachweis, Barrierefreiheits-Werkzeug) follow that switch and are not ticked here. Requires cvrt-legal 0.7.0+.

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": {
      "site": "<site>",
      "doc": "<doc>"
    },
    "name": "legal_put_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
docYesGenerated document: impressum, datenschutz or barrierefreiheit (BFSG statement, cvrt-legal 0.9.0+)
keepNoSlugs of sections added through the API that survive regeneration. REPLACES the stored list; omit to keep it
siteYesSite id (see list_sites)
enabledNomodule (section) key => on/off; merged into the stored selection
optionsNomodule key => { option key => on/off }; merged into the stored selection

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.14.0
    • changedInput schema / properties / enabled / description
      Previous value: -"module key => on/off"New value: +"module (section) key => on/off; merged into the stored selection"
    • changedInput schema / properties / keep / description
      Previous value: -"slugs of sections added through the API that survive regeneration"New value: +"Slugs of sections added through the API that survive regeneration. REPLACES the stored list; omit to keep it"
    • changedInput schema / properties / options / description
      Previous value: -"module key => { option key => on/off }"New value: +"module key => { option key => on/off }; merged into the stored selection"
  2. Addedv3.4.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: merge (not replace) semantics for the stored selection, 400 on unknown module/option keys, 409 preconditions, a version floor (cvrt-legal 0.7.0+), and an explicit statement that switch-bound sections (Einwilligungsnachweis, Barrierefreiheits-Werkzeug) cannot be ticked here. These are exactly the non-obvious traits an agent needs before mutating state.

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 core action and merge semantics are front-loaded, and every sentence carries information (errors, prerequisites, exclusions, version). It is dense to the point of being run-on, with inline German terms and parentheticals slightly interrupting the flow. Trimming the parenthetical UI reference would tighten it further.

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 5-parameter mutation tool with nested objects and no output schema, the description covers the return by proxy ('as legal_get_generator does'), the merge model, the prerequisite chain, failure codes, and edge cases around switch-bound sections. An agent has everything needed to invoke it correctly and interpret the result without further exploration.

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 description coverage is 100%, so the baseline is 3; the description goes beyond it by explaining that 'enabled' and 'options' are merged into the stored selection rather than replacing it, and that unknown keys are rejected with 400. The caveat that switch-tied sections are not settable here adds real semantic meaning about what values are valid. Minor gap: 'keep' replacement semantics live only in the schema.

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 opens with a specific verb pair and resource ('Tick or untick modules and options, then regenerate the document') and grounds it in a concrete UI equivalent ('the Datenschutz tab over the API'). It also distinguishes itself from its read sibling by noting it 'Returns the new state as legal_get_generator does', so an agent can separate the mutating tool from the getter 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?

It gives clear conditions and preconditions for calling: the library must be imported, and for datenschutz the required Impressum facts must be filled, both with 409 signals. It also carves out scope ('Sections tied to a switch ... are not ticked here'). What is missing is an explicit routing statement naming alternatives (e.g. legal_put_document, legal_put_facts) for the prerequisite steps, so the guidance is clear but not complete on when-not.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools