Skip to main content
Glama

NovaPixel LexGrid

gdpr_cmp_tracker_audit

Identifies installed Consent Management Platform (Iubenda, Cookiebot, OneTrust, etc.), audits Google Consent Mode v2 implementation and detects unconsented tracking scripts.

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
htmlContentNoRaw HTML content if URL cannot be fetched directly

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden. It does add real behavioral context beyond the name: the tool fetches the target site, performs three distinct analyses (CMP identification, Consent Mode v2 audit, script detection), and implies outbound network access to the supplied URL. It says nothing about whether the fetch is live, rate limits, failure behavior when the site blocks scraping, or what the audit report contains, which are significant gaps for a multi-step tool with zero annotation coverage.

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 dense sentence that front-loads the primary action and wastes no words. It is appropriately sized for the amount of information conveyed, though the three-in-one phrasing (identify, audit, detect) would scan better as an ordered list.

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

Completeness3/5

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

For a tool with no output schema and no annotations, the description covers the what but not the how-much or what-comes-back. An agent knows the intent but not the result shape, the depth of the audit, or the preconditions for success. Adequate as a minimum-viable definition, incomplete for a multi-analysis auditing tool.

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 fully documented in the schema, including the fallback relationship. The description adds no additional syntax, format, or precedence detail beyond that. Baseline 3 applies when the schema does the heavy lifting.

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?

The description names a specific verb set and resource: it identifies an installed Consent Management Platform by example (Iubenda, Cookiebot, OneTrust), audits Google Consent Mode v2, and detects unconsented tracking scripts. An agent can tell exactly what the tool produces at a high level. It does not differentiate itself from the closely related siblings (cookie_dark_patterns, eu_ai_act_check), which is the only thing keeping it from a 5.

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 mention of the sibling tools that overlap in GDPR/cookie auditing territory. The agent must infer from the name alone whether this is the right entry point versus cookie_dark_patterns or eu_ai_act_check. Only the implicit framing (audit a website's consent setup) hints at appropriate usage.

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