Skip to main content
Glama
Sign In

Checkbox

by site.checkbox
OverviewDiscussionsAdmin

Run a synthetic-shopper scan (write)

run_scan

WRITE: queues a real-browser scan of the site's sign-up / checkout and cancellation flow (1-3 minutes). Confirm with the user before calling repeatedly; scans count against fair-use limits. In live mode the account must be activated (verified domain). Poll get_scan until completed, then get_site_status or get_compliance_plan. After code changes prefer verify_task / verify_site, which pre-check instantly and queue the scan for you.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoSite id (site_…). Optional when the account has exactly one site in this mode; list_sites shows them.
regionsNoStates to scan from, e.g. ["US-CA"] (default: the site configuration).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), the description discloses the real-browser execution model, a 1-3 minute latency window, fair-use consumption per scan, and the verified-domain requirement in live mode. Those are exactly the operational facts an agent needs and none are derivable from the structured fields.

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?

Front-loaded with the "WRITE:" safety label followed by what gets queued and how long it takes, then constraints, then the follow-up workflow. Every clause carries actionable information with no filler or repetition of annotation content.

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?

No output schema exists and the tool is asynchronous, so the description compensates by naming the polling tool and the downstream reads that consume the result. For a two-parameter async write tool, nothing an agent needs in order to call 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 both `site` and `regions` are already documented in the schema with defaults and format hints. The description never mentions either parameter, so it adds no meaning beyond the schema; the 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?

Opens with an explicit verb and resource ("queues a real-browser scan") plus the specific flow being exercised (sign-up / checkout / cancellation) and expected duration. An agent can distinguish it from get_scan (read results), verify_task, and verify_site (pre-check alternatives) without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use and when-not-to-use routing: prefer verify_task / verify_site after code changes, poll get_scan while waiting, then follow with get_site_status or get_compliance_plan. It also names the precondition for live mode (activated account with verified domain) and warns to confirm with the user before repeated calls.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Checkbox 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