Skip to main content
Glama
Sign In

Bannerproof

by app.bannerproof
OverviewDiscussionsAdmin

Shareable report link

get_report_link
Idempotent

Creates (or returns the existing) private link to the latest report of a domain, for sending to a client or developer — opens without a login. 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_report_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe 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.0
Behavior4/5

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

The phrase 'Creates (or returns the existing)' is consistent with idempotentHint=true, so no contradiction, and it explains the reuse behavior in plain language. It also adds a genuinely useful non-annotation fact: the link opens without a login, i.e. anyone holding it can view the report — a security-relevant trait not captured by readOnlyHint/destructiveHint. It stops short of saying whether the link expires or can be revoked.

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?

A single dense sentence with the core action front-loaded and the purpose and applicability packed into trailing clauses. No filler, nothing repeated from the schema or annotations.

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 two-parameter, non-destructive, idempotent tool with no output schema, the description covers action, input applicability, and the key access property of the returned link. Missing only minor operational details such as link lifetime or revocation, which an agent could plausibly need.

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 both `domain` and `language` are already fully documented, and the description adds no format or behavior detail about them. Baseline 3 applies since the schema carries the parameter burden.

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 verb (creates/returns) and a specific resource (private link to the latest report of a domain), plus the intent (sending to a client or developer). It is clearly distinct from get_upgrade_link by resource type, though it never names that sibling to rule out confusion.

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 clear applicability context: 'Works for monitored domains and audited sites', which tells the agent which domain types are valid inputs. It does not state exclusions (e.g., what happens for unmonitored domains) or point to an alternative tool, so it stops short of full when/when-not guidance.

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