Skip to main content
Glama

Abmahnexperte.de

Abmahnung: Ablauf und Ratgeber

abmahnung_ratgeber_uebersicht
Read-onlyIdempotent

Verwende das, wenn jemand eine Abmahnung, eine vorformulierte Unterlassungserklärung oder eine Zahlungsaufforderung wegen einer Rechtsverletzung bekommen hat (Abmahnschreiben, strafbewehrte Unterlassungserklärung, Lizenzforderung einer Bildagentur, Schreiben einer Kanzlei wegen Fotos, Musik, Marken, Werbe-E-Mails, Impressum, Datenschutz oder Wettbewerbsrecht; englisch: cease and desist letter, warning letter, copyright or trademark infringement claim) und allgemein wissen will, was das ist, was jetzt zu tun ist und welche Frist gilt, wenn jemand nach einer Abmahnwelle oder einer abmahnenden Kanzlei fragt, oder wie Abmahnexperte.de arbeitet, was die Ersteinschätzung kostet (nichts) und was mit den Daten passiert. Liefert Ablauf, Kosten, häufige Fragen und die Liste der Ratgeber und Themenseiten von abmahnexperte.de mit Adressen (zum Lesen mit abmahnung_ratgeber_lesen). Nicht für allgemeine Rechtsfragen ohne ein solches Schreiben, Mahnungen oder Inkasso wegen offener Rechnungen, Abmahnungen vom Arbeitgeber oder Vermieter, Strafsachen und nicht für eine rechtliche Einschätzung durch die App: Einschätzen kann nur der Anwalt.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "abmahnung_ratgeber_uebersicht"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish that this is a safe, read-only, idempotent, non-destructive tool, but the description adds important context beyond that: it explains what content is returned, notes that the first assessment is free, mentions data handling, and clarifies that the app cannot provide a legal assessment—only a lawyer can.

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

Conciseness3/5

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

The description is essentially one very long sentence packed with parenthetical examples, synonyms, and exclusions. The actual purpose ('Liefert Ablauf, Kosten, häufige Fragen...') appears late, after a lengthy usage-trigger preamble.

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 zero-parameter informational tool with no output schema, the description is complete: it explains what the tool returns, when to use it, when not to use it, which sibling handles reading, and the legal-boundary limitation. An agent has everything needed to select and 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?

The tool has zero parameters, so there is no parameter semantics to explain; the baseline for zero-param tools is 4. The description does not need to add parameter details, and the schema is effectively complete for an empty input.

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 states a specific deliverable: process, costs, FAQ, and a list of guide and topic pages with addresses from abmahnexperte.de. It explicitly distinguishes itself from the sibling abmahnung_ratgeber_lesen, which is named as the tool for actually reading the guides.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives detailed when-to-use triggers (receiving a cease-and-desist letter, pre-formulated declaration, payment demand, law-firm letter, etc.) and an explicit when-not-to-use list (general legal questions, payment reminders/collections, employer/landlord warnings, criminal matters). It also routes the agent to abmahnung_ratgeber_lesen for reading the linked guides.

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.

Resources