Skip to main content
Glama

DSGVO.pro — German Digital-Law Compliance

Get Scan Report

get-scan-result
Read-onlyIdempotent

Get the full compliance report for a completed scan. Returns score (0–100), financial risk in EUR, per-module results, and all violations with law references, fine estimates, and fix instructions. ⚠️ Only call after the scan is complete — check status first with get-scan-status. If called while scan is still running, returns current progress instead of an error.

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": {
      "scanId": "<scanId>"
    },
    "name": "get-scan-result"
  }
}

Input Schema

NameRequiredDescriptionDefault
scanIdYesThe scan ID returned by check-compliance

Output Schema

NameRequiredDescriptionDefault
urlNo
errorNo
scoreNoCompliance score 0–100 (completed scans only)
scanIdNo
statusNoinitializing | pending | crawling | scanning | completed | failed | cancelled
messageNo
modulesNo
offerUrlNoOpens the fix-offer request for this scan on dsgvo.pro
riskLevelNo
startedAtNoISO timestamp
violationsNo
completedAtNoISO timestamp
modulesTotalNo
riskAmountMaxNo
riskAmountMinNo
scanReportUrlNoHuman-readable report on dsgvo.pro
screenshotUrlNoPublic screenshot of the scanned page
modulesCompletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / violations / items / properties / belegteFaelle
      Added value: +{
      +  "description": "Court decisions with file number and source that put a real amount on this kind of violation; empty when none is verified. Not a prediction for this site.",
      +  "items": {
      +    "properties": {
      +      "aktenzeichen": {
      +        "type": "string"
      +      },
      +      "art": {
      +        "type": "string"
      +      },
      +      "betragEur": {
      +        "type": "number"
      +      },
      +      "datum": {
      +        "description": "ISO date of the decision",
      +        "type": "string"
      +      },
      +      "gericht": {
      +        "type": "string"
      +      },
      +      "hinweis": {
      +        "type": "string"
      +      },
      +      "quelle": {
      +        "type": "string"
      +      },
      +      "zusammenfassung": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. Changed4 schema fields changed
    • addedOutput schema / properties / offerUrl
      Added value: +{
      +  "description": "Opens the fix-offer request for this scan on dsgvo.pro",
      +  "type": "string"
      +}
    • addedOutput schema / properties / riskAmountMax
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / riskAmountMin
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / screenshotUrl
      Added value: +{
      +  "description": "Public screenshot of the scanned page",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. Changed1 schema field changed
    • changedOutput schema / properties / status / description
      Previous value: -"initializing | pending | crawling | scanning | completed | failed"New value: +"initializing | pending | crawling | scanning | completed | failed | cancelled"
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "completedAt": {
      +      "description": "ISO timestamp",
      +      "type": "string"
      +    },
      +    "error": {
      +      "type": "string"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "modules": {
      +      "items": {
      +        "properties": {
      +          "maxScore": {
      +            "type": "number"
      +          },
      +          "module": {
      +            "type": "string"
      +          },
      +          "score": {
      +            "type": "number"
      +          },
      +          "status": {
      +            "type": "string"
      +          },
      +          "violationsCount": {
      +            "type": "number"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "modulesCompleted": {
      +      "type": "number"
      +    },
      +    "modulesTotal": {
      +      "type": "number"
      +    },
      +    "riskLevel": {
      +      "type": "string"
      +    },
      +    "scanId": {
      +      "type": "string"
      +    },
      +    "scanReportUrl": {
      +      "description": "Human-readable report on dsgvo.pro",
      +      "type": "string"
      +    },
      +    "score": {
      +      "description": "Compliance score 0–100 (completed scans only)",
      +      "type": "number"
      +    },
      +    "startedAt": {
      +      "description": "ISO timestamp",
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "initializing | pending | crawling | scanning | completed | failed",
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "violations": {
      +      "items": {
      +        "properties": {
      +          "bussgeldrahmen": {
      +            "properties": {
      +              "amountEur": {
      +                "type": "number"
      +              },
      +              "currency": {
      +                "type": "string"
      +              },
      +              "paragraph": {
      +                "type": "string"
      +              }
      +            },
      +            "type": [
      +              "object",
      +              "null"
      +            ]
      +          },
      +          "fixSteps": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "fixSummary": {
      +            "type": "string"
      +          },
      +          "law": {
      +            "description": "Law and paragraph, e.g. \"BGB §356a\"",
      +            "type": "string"
      +          },
      +          "module": {
      +            "type": "string"
      +          },
      +          "noBussgeldReason": {
      +            "description": "Why no fine range applies, when bussgeldrahmen is null",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "severity": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral information: calling during a running scan returns progress rather than an error, which prevents an agent from treating a thin response as a failure. It partly duplicates the output schema by listing return fields.

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?

Three tight sentences: purpose and payload first, then the prerequisite and the sibling to use, then the edge-case behavior. The warning marker is front-loaded on the critical constraint, and nothing is redundant.

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?

Given an output schema exists, return values need not be exhaustively documented, yet the description still summarizes them. With one fully documented parameter, complete safety annotations, and the early-call behavior explained, an agent has everything needed to invoke this correctly.

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?

There is a single parameter with 100% schema description coverage ('The scan ID returned by check-compliance'), so the schema carries the semantics. The description adds no further guidance about scanId format or validity, which is acceptable at this coverage level but earns only the baseline.

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 ('Get the full compliance report for a completed scan') and immediately enumerates the payload contents (score, financial risk in EUR, per-module results, violations with law references). This is clearly distinguishable from get-scan-status, which merely reports progress.

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?

Explicitly names the prerequisite and the sibling to call first: 'Only call after the scan is complete — check status first with get-scan-status.' It also describes the degradation path if the condition is violated, so an agent knows the consequence rather than guessing.

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