Skip to main content
Glama

legal_put_facts

Update Impressum fields by merging only the keys you pass, clearing fields with empty strings, and regenerating all generated documents. Invalid keys, select values, or emails are refused.

Instructions

Set Impressum fields. Merges: only the keys given change; an empty string clears a field. An unknown key, a value outside a select field's options or an invalid email is refused (400); a checkbox field stores "ja" or empty. Needs an imported Impressum library (409 otherwise). Regenerates every generated document and returns the new state as legal_get_facts does. 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>",
      "facts": "<facts>"
    },
    "name": "legal_put_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
factsYesfield key => value, keys as legal_get_facts lists them

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.4.0

TDQS

A4.7/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 behavioral burden and does so: it discloses merge rather than replace semantics, the empty-string clear convention, validation failure modes returning 400, checkbox value coercion to "ja", the 409 library prerequisite, and the significant side effect that every generated document is regenerated.

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

Conciseness5/5

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

Five tightly packed sentences, each adding a distinct operational fact, front-loaded with the primary action and followed by merge rules, error behavior, and prerequisites in a logical order. No filler.

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 nested-object mutation tool with no output schema, the description compensates by specifying the return shape indirectly ("returns the new state as legal_get_facts does") and by covering error codes, prerequisites, and the document-regeneration side effect. An agent has enough to invoke it correctly.

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 genuine meaning beyond the schema: only supplied keys mutate, an empty string clears a field, checkbox fields accept "ja" or empty, and invalid values for select fields or emails are rejected. It does not describe the shape or limits of the facts object beyond key naming.

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 opening sentence names a specific verb and resource ("Set Impressum fields") and immediately clarifies the merge semantics, which distinguishes this mutation tool from the legal_get_facts reader and from the other legal_put_* writers covering different domains.

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 states the precondition for use (an imported Impressum library is required, 409 otherwise) and points to legal_get_facts for how keys are named and what the resulting state looks like. It does not explicitly enumerate when to prefer a sibling writer instead, but the domain scoping to Impressum makes that largely self-evident.

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