Skip to main content
Glama

UAI x402 Security Tools

gdpr-privacy-scan

Scan a website landing page for GDPR and CCPA privacy signals — privacy policy links, cookie consent language, and compliance keyword coverage for agent audits. (REST equivalent: POST /api/v1/gdpr-privacy-scan, $0.08)

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": "gdpr-privacy-scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to scan for GDPR/privacy signals

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the full behavioral burden. It usefully discloses the $0.08 cost and the REST endpoint backing the tool, and 'scan' implies a read-only fetch, but it never says whether a live HTTP request is made, how redirects or JS-rendered pages are handled, or whether results are cached.

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 dense sentence front-loads the action, the target, and the detectable signals, followed by a compact parenthetical for endpoint and price. Nothing is redundant, though the phrase 'for agent audits' is slightly vague relative to the rest of the sentence.

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?

For a one-parameter read-only scan with no output schema, the description adequately conveys what categories of findings come back. The main residual gap is the absence of any note on result format or how findings are graded, which matters somewhat for an audit-oriented 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?

There is a single required parameter with 100% schema description coverage ('URL to scan for GDPR/privacy signals'), so the schema already does the work. The description adds only the 'landing page' scoping nuance, which usefully hints that a single page rather than a whole site is analyzed, but nothing about URL format or validation.

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?

The description names a specific verb ('Scan'), a specific resource ('a website landing page'), and enumerates exactly what it detects: privacy policy links, cookie consent language, and compliance keyword coverage. That level of specificity separates it cleanly from sibling scans such as secret-scan or cve-lookup, which target entirely different artifacts.

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 implied by 'for agent audits,' which signals a compliance-assessment context, but there is no explicit statement of when to choose this over related scans or when it is inappropriate. The REST equivalent and price are mentioned but no preconditions (e.g., publicly reachable page) are 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