Skip to main content
Glama

gdpr_cmp_tracker_audit

Read-onlyIdempotent

[Web DOM inspection. Read-only, non-destructive, side-effect free]. Identifies installed Consent Management Platforms (Iubenda, Cookiebot, OneTrust, Didomi), audits Google Consent Mode v2 implementation, and detects unconsented third-party tracking scripts loaded prior to user consent. Usage: Use this tool to audit cookie consent compliance under GDPR Article 7. For cookie banner deceptive design and dark pattern checks, use 'cookie_dark_patterns' instead. Returns: JSON object with { cmpDetected: string | null, consentModeV2: { enabled: boolean, defaultState: string }, preConsentTrackersFound: string[], gdprComplianceStatus: 'COMPLIANT' | 'NON_COMPLIANT', violations: string[] }.

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": "gdpr_cmp_tracker_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoTarget website URL to fetch and audit (e.g. https://novapixel.it)
htmlContentNoRaw HTML content if URL cannot be fetched directly

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Target website URL to fetch and audit"New value: +"Target website URL to fetch and audit (e.g. https://novapixel.it)"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this as a read-only, side-effect-free Web DOM inspection while adding genuinely new context: it fetches a live URL and inspects the DOM. The 'Returns' block also discloses the exact result shape, which is valuable since no output schema exists. It stops short of stating failure behavior when the URL cannot be fetched or how the htmlContent fallback interacts with url.

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?

Front-loaded with a capability statement, then a Usage line, then a Returns line — a clean, scannable structure with no filler prose. The bracketed preamble partially repeats what the annotations already say about read-only and side-effect freedom, a minor redundancy.

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?

No output schema exists, so the description compensates by enumerating the return fields and their types, and it covers both input parameters via the schema. For a two-parameter read-only audit tool, nothing an agent needs to invoke or interpret it is missing.

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?

Schema description coverage is 100%, so both parameters (url and htmlContent) are already documented in the schema. The description adds nothing about precedence between url and htmlContent or supported formats, so baseline 3 applies.

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 ('Identifies installed Consent Management Platforms', 'audits Google Consent Mode v2', 'detects unconsented third-party tracking scripts') and names the concrete CMPs it recognizes. The final clause explicitly separates it from the sibling 'cookie_dark_patterns', so an agent can route correctly without opening a schema.

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?

Gives an explicit when-to-use ('audit cookie consent compliance under GDPR Article 7') and an explicit when-not-to-use with the named alternative ('For cookie banner deceptive design and dark pattern checks, use cookie_dark_patterns instead'). This is the strongest form of routing guidance.

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