Skip to main content
Glama
Sign In

Bannerproof

by app.bannerproof
OverviewDiscussionsAdmin

Evidence pack (CSV/JSON)

get_evidence
Idempotent

Evidence pack of the latest scan of a domain: every tracker request in order with its phase (before consent / after Reject) and time, plus the cookies and consent signals. Returns a summary and download links (CSV and JSON, open without a login) for a client, a developer or a dispute. Works for monitored domains and audited sites.

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

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Adds behavior the annotations don't cover: the pack is scoped to the *latest* scan, links open without a login, and it applies to both monitored domains and audited sites. Annotations only supply the safety/idempotency profile, so this access-and-scope context is genuinely additive. Missing only edge-case behavior such as what happens if no scan exists.

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?

Two sentences, front-loaded with what the pack contains, then the return shape and audience. The middle clause is dense with lists but every item is informative rather than 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?

There is no output schema, so the description carries the return-value burden and does so: a summary plus CSV/JSON download links. Combined with 100% schema coverage and annotations, an agent has enough to call it correctly; only failure/precondition behavior is unstated.

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?

Only one parameter and schema coverage is 100%, so the schema already documents 'domain' fully. The description reinforces that the pack is scoped to a single domain but adds no format, normalization, or validation detail beyond the schema. Baseline 3 applies.

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?

States a specific resource (evidence pack of the latest scan of a domain) and enumerates its contents: ordered tracker requests with phase (before consent / after Reject) and timestamp, cookies and consent signals. That is far more concrete than siblings like get_findings or get_report_link, though it never names those siblings to draw the boundary explicitly.

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?

Gives concrete use cases ('for a client, a developer or a dispute') and states applicability ('Works for monitored domains and audited sites'), which tells the agent when this is the right tool. It stops short of naming an alternative or an exclusion condition (e.g. what to use when no scan has run yet).

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