Skip to main content
Glama

Check what loads before consent (free)

pre_consent_scan
Read-onlyIdempotent

Free, no sign-in: fetch a public page as a first-time visitor and report which trackers (GA4, Google Ads, Meta Pixel, TikTok, LinkedIn, Hotjar…) and cookies load before the visitor consents, which ones wait, which other sites the page contacts (e.g. Google Fonts), and how to fix it. Static check of the HTML and headers (no JavaScript runs). Limited to 10 checks per hour per visitor.

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": {
      "url": "<url>"
    },
    "name": "pre_consent_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic page to check, e.g. https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only/idempotent/non-destructive, so the bar is lower, and the description adds real value beyond them: the scan is static only ('no JavaScript runs'), the visitor is treated as a first-time visitor with no consent, and there is a concrete rate limit of 10 checks/hour per visitor. These are exactly the operational constraints an agent needs before calling.

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?

One front-loaded sentence with the key constraints (free, no sign-in, static, rate limit) placed before the parenthetical tracker examples. It is somewhat run-on with the long '…' list, but no sentence is filler.

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?

No output schema exists, and the description compensates by listing what the report contains: pre-consent trackers, deferred trackers, contacted third parties, and fix advice. An agent could call this confidently; only minor gaps remain (response format, behavior on unreachable pages).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single url parameter, so baseline would be 3. The description adds meaning the schema does not: the URL is fetched as an unauthenticated first-time visitor with no stored consent, which is what makes the result meaningful. It stops short of any format or reachability constraints.

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?

Uses a specific verb+resource ('fetch a public page as a first-time visitor and report which trackers and cookies load before consent') and enumerates the concrete findings returned (GA4, Meta Pixel, third-party hosts, remediation). It never names the obvious sibling run_compliance_scan, so the agent must infer the boundary between this free static check and the fuller scan.

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

Usage Guidelines3/5

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

'Free, no sign-in' and the 10-checks-per-hour cap imply a lightweight pre-check use case, but there is no explicit statement of when to prefer this over run_compliance_scan or configure_banner, and no when-not-to-use guidance. The usage context is implied rather than stated.

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