Skip to main content
Glama

Run compliance scan

run_compliance_scan

Scan a public web page for trackers (GA4, Google Ads, GTM, Meta Pixel, Hotjar, TikTok, LinkedIn…), cookies and Consent Mode setup, and get a 0–100 consent setup score with the reason for its grade (read from the page's HTML; not legal advice). Anything confirmed loading before consent caps the grade at D; what can't be confirmed lowers confidence, not the grade. Scans of your own domains are saved; apply=true adds the detected services to that site's banner.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL, e.g. https://example.com
langNoLanguage of the grade reason (default en).
applyNoAdd detected services and cookie names to the site's banner.
site_idNoSave the scan to this site (otherwise matched by domain).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "Language of the grade reason (default en).",
      +  "enum": [
      +    "en",
      +    "fr",
      +    "de",
      +    "it",
      +    "es"
      +  ],
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / site_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations say readOnlyHint=false and openWorldHint=true; the description adds real context beyond that — grading rules (confirmed pre-consent loading caps at D, unconfirmed items only lower confidence), the HTML-only basis and 'not legal advice' disclaimer, the saving side effect for owned domains, and the mutation triggered by apply=true. Missing are auth/prerequisite notes or rate-limit expectations for an open-world scanner.

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?

Three sentences, front-loaded with what is scanned and what is returned, then grading semantics, then side effects. The parenthetical tracker list and 'not legal advice' aside are slightly dense but each carries selection-relevant information.

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?

With no output schema, the description correctly explains the return value (0–100 score plus reason) and covers the mutation path via apply/site_id. For a four-parameter open-world scan tool it is nearly complete, lacking only prerequisite/auth context.

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 all four parameters are already documented; the description mainly reinforces apply=true and the domain-matched saving behavior. The one genuinely additive detail is the 'public web page' constraint on url, which narrows valid inputs beyond the schema's generic 'Page URL' example.

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 opens with a concrete verb+resource ('Scan a public web page') and enumerates exactly what is detected (GA4, GTM, Meta Pixel, Hotjar, cookies, Consent Mode) plus the 0–100 score output. It never names or contrasts the sibling tools pre_consent_scan or consent_mode_check, so an agent cannot tell from this text alone which scan variant to pick.

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?

Usage is only implied: the text explains that scans of your own domains are saved and that apply=true writes to the banner, which hints at when the tool is appropriate, but there is no explicit when-to-use/when-not guidance relative to the other scan tools in the catalog.

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