Skip to main content
Glama
Sign In

Bannerproof

by app.bannerproof
OverviewDiscussionsAdmin

Add a domain to monitoring

add_domain
Idempotent

Adds a domain to weekly monitoring in the connected account (within the plan's domain limit) and runs its first scan. Requires a plan with a free domain slot; otherwise it returns an error that names the plan 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": {
      "domain": "<domain>"
    },
    "name": "add_domain"
  }
}

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.2/5.0
Behavior4/5

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

Annotations already declare write, non-destructive, idempotent, open-world. The description adds substantive context the annotations lack: monitoring is weekly/recurring, a first scan is triggered as an immediate side effect, and there is a plan-slot quota that can reject the call. It stops short of saying what happens on re-adding an existing domain or how the initial scan's results are retrieved.

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, no filler: the first states the action and side effect, the second the precondition and failure mode. Information is front-loaded in the correct priority order.

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?

With no output schema and only two fully documented params, the description covers the key unknowns an agent faces: quota precondition, error shape, and the automatic first scan. Slightly incomplete on the idempotency edge case (re-adding an existing domain) given idempotentHint=true.

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%, including a full language enumeration, so the schema carries parameter meaning. The description adds only the plan-limit context and says nothing about the optional language parameter, so baseline 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?

Specific verb and resource ('Adds a domain to weekly monitoring in the connected account') plus the immediate consequence (runs its first scan). This distinguishes it from sibling scanning tools like scan_domain, audit_domain, and quick_check, which operate on already-tracked targets.

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?

States a clear precondition — a plan with a free domain slot — and what happens when it fails (an error naming the plan needed). It does not, however, explicitly contrast with siblings such as list_domains or scan_domain, so the agent must infer the 'when' from the purpose statement.

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