Skip to main content
Glama
Sign In

Bannerproof

by app.bannerproof
OverviewDiscussionsAdmin

Explain a finding

explain_finding
Read-only

Explains one finding in plain language: what it is, why it is a problem, how to fix it and which rule it relates to. Pass the tracker name exactly as get_findings returned it. Free, no account needed.

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": {
      "tracker": "<tracker>"
    },
    "name": "explain_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoWhat was found: fired_before_consent (default), still_active_after_reject, missing_reject_option, tcf_consent_after_reject or gpc_ignored
trackerYesThe tracker or cookie name from get_findings, e.g. 'Meta (Facebook) Pixel' or '_ga cookie'
languageNoLanguage for the fix instructions: en, de, fr, es, it, nl, da, sv, fi, no, et, pl or pt. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the description only needs incremental context. It adds real value by disclosing that no account or authentication is required and that the tracker string must be an exact match from get_findings, which implies a lookup that silently fails on mismatched names. Return format details and any rate limits are left unstated.

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?

Two sentences, front-loaded with the core action and the content of the explanation, followed by the critical parameter constraint. Every clause carries information an agent needs; nothing is padding.

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 compensates by describing what the explanation returns (definition, problem rationale, fix, related rule). It also covers the input constraint, the auth-free nature, and the prerequisite tool. Nothing an agent needs to invoke it correctly is missing.

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 all three parameters (tracker, status, language) are fully documented in the schema, including the status enum values and language codes. The description only reinforces the exact-match requirement for tracker, which the schema already states. Baseline 3 applies since the schema does the heavy lifting.

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 (explains) and resource (one finding) and enumerates exactly what the explanation covers: what it is, why it is a problem, how to fix it, and which rule it relates to. Clearly distinguishable from sibling tools like get_findings, which retrieve findings rather than explain them.

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?

The instruction 'Pass the tracker name exactly as get_findings returned it' implicitly establishes get_findings as the prerequisite and warns against reformatting the name. It also notes 'Free, no account needed,' signalling it is usable without an authenticated audit. No explicit when-not-to-use or alternative-tool routing is given, so it falls short of a 5.

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