Skip to main content
Glama
Sign In

Bannerproof

by app.bannerproof
OverviewDiscussionsAdmin

Status of several audits

get_audits_status
Read-only

Status of several audits at once (e.g. the job_ids audit_domains returned): which are done with their score and issue count, which are still running, and which failed — with the reason. Failed scans are not charged: their audit credit goes back to the account automatically.

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": {
      "job_ids": "<job_ids>"
    },
    "name": "get_audits_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idsYesThe job_ids from audit_domains or audit_domain — up to 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / job_ids / description
      Previous value: -"The job_ids from audit_domains or audit_domain — up to 20"New value: +"The job_ids from audit_domains or audit_domain — up to 10"
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior: failed scans are not charged and their audit credit is refunded automatically, which informs retry decisions. It doesn't cover polling expectations or result ordering, keeping it off a 5.

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 tight sentences, front-loaded with the core purpose, then the outcome categories and a credit-refund note. Every clause carries information, though the parenthetical example slightly interrupts the flow.

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 and a single required parameter, the description fully covers what the agent needs: where job_ids come from, what states to expect, and the billing implication of failures. Nothing essential for correct invocation 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 coverage is 100% and the single job_ids parameter is documented in the schema, including the 'up to 10' limit. The description only adds provenance ('the job_ids audit_domains returned'), which is useful but marginal, so the 3 baseline 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 concrete verb and resource ('Status of several audits') and immediately clarifies the batch nature ('at once'), which implicitly separates it from the singular get_scan_status sibling. The description also enumerates the three outcomes (done with score and issue count, running, failed with reason), so an agent knows exactly what this returns.

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 a clear triggering context — 'the job_ids audit_domains returned' — which tells the agent to call this after launching audits via audit_domains/audit_domain. It does not enumerate when-not-to-use or explicitly name get_scan_status as the single-audit alternative, so it stops 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