Skip to main content
Glama

NovaPixel LexGrid

cookie_dark_patterns

Automated audit of cookie banners and consent modals for illegal dark patterns under EDPB 03/2022 and Garante Privacy guidelines: asymmetric styling, missing first-layer reject, pre-ticked checkboxes and confirmshaming.

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

Input Schema

NameRequiredDescriptionDefault
urlNoTarget website URL to fetch and audit
htmlContentNoRaw HTML content of page or CMP banner

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose meaningful substance about what is inspected and the legal basis (EDPB 03/2022, Garante guidelines), but it omits operational behavior: that 'url' triggers a network fetch, whether the tool is strictly read-only, and what happens when neither optional parameter is supplied.

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?

A single front-loaded sentence that names the action, the legal frameworks, and the pattern taxonomy without padding. The long enumeration is dense but each item earns its place by defining detection scope.

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

Completeness2/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 should at least sketch what an audit returns (violations found, per-pattern verdicts, severity), and it does not. Combined with the absence of annotations and the unexplained url/htmlContent choice, an agent cannot tell what to expect from a call.

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 coverage is 100%, so both parameters are already documented in the schema and the baseline of 3 applies. The description adds no meaning beyond that — it never explains the relationship between 'url' and 'htmlContent' or which one is authoritative if both are given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('automated audit of cookie banners and consent modals') and enumerates the exact defect classes it looks for (asymmetric styling, missing first-layer reject, pre-ticked checkboxes, confirmshaming). It does not, however, distinguish itself from the sibling gdpr_cmp_tracker_audit, which plausibly overlaps on consent-banner auditing.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no routing to alternatives such as gdpr_cmp_tracker_audit. Critically, it never says when to pass 'url' versus 'htmlContent' versus both, which is the main decision an agent faces here.

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