Skip to main content
Glama
Sign In

Bannerproof

by app.bannerproof
OverviewDiscussionsAdmin

Quick consent check (free)

quick_check
Read-only

Free check, no account needed: opens a public website like a first-time visitor and reports whether trackers or third-party requests fire before the visitor consents (GDPR/ePrivacy), with a 0–100 score. Returns only yes/no and the score; the full findings (which trackers, the exact requests, how to fix each one) are available with a connected Bannerproof account (get_findings). Results are cached for up to 7 days. This is an automated technical check, not legal advice.

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": {
      "domain": "<domain>"
    },
    "name": "quick_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe website's domain, e.g. example.com
languageNoLanguage for the fix instructions and report links: en, de, fr, es, it, nl, da, sv, fi, no, et, pl or pt. Normally the language of the conversation. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the readOnly/openWorld annotations: results are cached up to 7 days, only yes/no plus score are returned, deeper findings require a connected account, and it is an automated check rather than legal advice. These disclosures directly shape how an agent should interpret and present output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences with zero filler; the free/no-account hook and the tracker-before-consent purpose are front-loaded, with limitations and disclaimers following. Every sentence carries distinct information.

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

Completeness5/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 covers the return values (yes/no and score), the caching behavior, and the escalation path to get_findings. An agent has everything needed to call and interpret the result.

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 the domain and language parameters are fully documented in the schema. The description adds no parameter-level detail beyond the implicit notion of checking a website, so the baseline of 3 applies.

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?

States a specific verb and resource: opens a public website as a first-time visitor and reports whether trackers fire before consent, with a 0-100 score. This is clearly distinguishable from get_findings, which it names as the full-detail sibling.

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

Usage Guidelines4/5

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

Explicitly frames the tool as free with no account needed and points to get_findings for the full results, giving clear context for when to use it. It does not, however, route the agent away from similar siblings such as scan_domain or audit_domain, so the alternative comparison is incomplete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Bannerproof toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources