Skip to main content
Glama

DSGVO.pro — German Digital-Law Compliance

Check Scan Progress

get-scan-status
Read-onlyIdempotent

Lightweight progress check for an in-progress compliance scan. Returns current status (pending/crawling/scanning/completed/failed) and how many modules have finished (20 Standard or up to 33 with Pro/Agency tier including Hosting-Standort (Schrems II) (Art. 13 lit. f DSGVO), Widerrufsbutton (§356a BGB), KI-Transparenz (Art. 50 KI-VO), Tech-Stack-Aktualität (Art. 32 DSGVO), Anwaltsspezifische Prüfung (BORA / BRAO), Maklerspezifische Prüfung (§34c GewO + MaBV + GEG), Arztspezifische Prüfung (BOÄ + HWG + Art. 9 DSGVO), Finanzvermittler-Prüfung (§34d/f/h/i GewO + FinVermV), Gastronomie-Prüfung (LMIV + PAngV + IfSG), Kosmetik-Prüfung (KosmetikV + HWG + UWG), Bau-/Sanierung-Prüfung (§34c GewO + HwO + MiLoG), Hotel-/Beherbergung-Prüfung (BMG + PAngV + GEG + DSGVO)). Use this to poll progress. When status is 'completed', call get-scan-result for the full report.

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-status"
  }
}

Input Schema

NameRequiredDescriptionDefault
scanIdYesThe scan ID returned by check-compliance

Output Schema

NameRequiredDescriptionDefault
urlNo
errorNo
readyNotrue once the scan is completed or failed
scanIdNo
statusNoinitializing | pending | crawling | scanning | completed | failed | cancelled
messageNo
startedAtNoISO timestamp
modulesTotalNo
modulesRunningNo
modulesCompletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "error": {
      +      "type": "string"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "modulesCompleted": {
      +      "type": "number"
      +    },
      +    "modulesRunning": {
      +      "type": "number"
      +    },
      +    "modulesTotal": {
      +      "type": "number"
      +    },
      +    "ready": {
      +      "description": "true once the scan is completed or failed",
      +      "type": "boolean"
      +    },
      +    "scanId": {
      +      "type": "string"
      +    },
      +    "startedAt": {
      +      "description": "ISO timestamp",
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "initializing | pending | crawling | scanning | completed | failed",
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered. The description adds beyond that by disclosing the status state machine (pending/crawling/scanning/completed/failed) and tier-dependent module counts, which is genuinely useful for deciding how to interpret a poll. It does not mention polling cadence or whether the status payload changes between calls.

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

Conciseness2/5

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

The opening sentence and the closing routing instruction are well front-loaded, but the middle is dominated by a 13-item enumeration of Pro/Agency module names with legal citations. None of that list helps an agent decide to call this tool or how to call it, and it buries the two sentences that matter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter polling tool with an output schema and full annotations, the description covers purpose, the status values, and the handoff to get-scan-result. What an agent needs in order to call it correctly is present; the only omission is guidance on polling frequency or terminal states beyond 'completed'.

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 meaning. The description adds nothing about scanId — no format, no validity window — which is the baseline 3 for a fully documented 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?

States a specific verb and resource ('Lightweight progress check for an in-progress compliance scan') and immediately pins down what is returned. It distinguishes itself from get-scan-result by name, so an agent can tell the two apart without opening either 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?

'Use this to poll progress' plus 'When status is completed, call get-scan-result for the full report' gives clear usage context and names the alternative with the condition that selects it. It stops short of exclusions (e.g. don't poll after completion or for a failed scan), so it is strong but not exhaustive.

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