rechtsklar24

Gesetzlicher Bußgeld- oder Strafrahmen

get_fine_ceilings

Read-onlyIdempotent

Use for "wie hoch ist das Bußgeld", "Strafe", "was droht", "Höchstbetrag", "Vertragsstrafe Abmahnung" in German e-commerce law: BFSG, Preisangabenverordnung, Cookies/TDDDG, Verpackungsgesetz, Elektrogesetz, DSGVO, Produktsicherheit (ProdSG/GPSR), Vertragsstrafe bei der ersten Abmahnung (§ 13a UWG). Returns the statutory maximum from the source register with paragraph, URL and check date. It is always the legal ceiling, never an estimate for a specific case or shop.

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": {
      "thema": "<thema>"
    },
    "name": "get_fine_ceilings"
  }
}

Input Schema

Name	Required	Description	Default
`thema`	Yes	bfsg, pangv, cookies_tdddg, verpackg, elektrog, dsgvo, prodsg_gpsr oder abmahnung_vertragsstrafe.

Output Schema

Name	Required	Description	Default
`stand`	No
`thema`	Yes
`titel`	Yes
`fakten`	Yes
`hinweis`	Yes
`info_url`	Yes
`disclaimer`	Yes
`register_url`	Yes
`hoechstrahmen`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint and openWorldHint=false, so the safety profile is settled. The description adds real context beyond that: results carry paragraph, URL and check date, and the value is strictly a statutory ceiling rather than a case-specific figure. Auth needs and rate limits are not mentioned, keeping it at 4.

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?

Usage triggers are front-loaded and the disambiguating scope sentence closes the text; the quoted user phrasings are dense but each maps to a real query pattern. Slightly long but nothing is 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?

With an output schema present, return values need no explanation, and the description covers the domain, the permitted topics, and the semantics of the returned figure. An agent has everything needed to call 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% and the single enum parameter is self-describing, so the baseline is 3. The description goes further by expanding the cryptic enum tokens into legal areas (cookies_tdddg → 'Cookies/TDDDG', abmahnung_vertragsstrafe → 'Vertragsstrafe bei der ersten Abmahnung (§ 13a UWG)', prodsg_gpsr → 'ProdSG/GPSR'), which genuinely aids value selection.

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 the statutory maximum from the source register with paragraph, URL and check date') and scopes it to named German e-commerce statutes, which cleanly separates it from calculate_grundpreis, get_obligation_dates and get_study_facts.

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 trigger phrasings ('wie hoch ist das Bußgeld', 'Strafe', 'Höchstbetrag') and a negative boundary ('always the legal ceiling, never an estimate for a specific case or shop'). It does not name a sibling tool as the alternative route, so it falls short of a 5.

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

All rechtsklar24 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?