Skip to main content
Glama
Sign In

Checkbox

by site.checkbox
OverviewDiscussionsAdmin

Re-check the whole site now

verify_site
Idempotent

Re-reads the connected billing platform (Stripe portal, prices, Checkout Sessions; rate-limited), re-fetches the registered policies, pre-checks the checkout, re-evaluates every law and queues a scan. Use it for the first check after setup, after deploying several changes, after changing a Stripe setting, or when the plan looks stale. Waits up to wait seconds, then call get_compliance_plan.

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

Input Schema

NameRequiredDescriptionDefault
siteNoSite id (site_…). Optional when the account has exactly one site in this mode; list_sites shows them.
waitNoSeconds to wait for the result before answering (0-30; larger values wait 30; default 25). Use 0 to return at once and poll later.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses rate-limiting on the external billing platform, enumerates the remote systems touched (open-world consistent), documents the blocking wait behavior with its cap, and states that a scan is queued rather than completed synchronously. This matches idempotentHint and destructiveHint=false without contradicting them.

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?

Front-loaded with the action, then usage triggers, then the wait/follow-up instruction – logical ordering with no filler. The first sentence is long and clause-heavy, which slightly reduces scannability, but every clause carries information.

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, the description correctly redirects to get_compliance_plan for results and explains the wait/poll path, so an agent can call it and know what to do next. Minor gap: it doesn't say what happens if the scan cannot complete within the wait window beyond 'poll later'.

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%, so both site and wait are already documented in the schema. The description only restates the wait semantics ('waits up to `wait` seconds') without adding format or edge-case detail beyond the schema's 0-30/default-25 explanation. Baseline 3 applies when the schema does the heavy lifting.

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?

States specific verbs and resources: re-reads Stripe portal/prices/Checkout Sessions, re-fetches policies, pre-checks checkout, re-evaluates laws, queues a scan. This is clearly a full-site re-verification, distinguishable from run_scan and get_compliance_plan, which appear only as the follow-up step.

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?

Explicitly enumerates when to use: first check after setup, after deploying several changes, after changing a Stripe setting, or when the plan looks stale. It also names the required follow-up (call get_compliance_plan after waiting), so the workflow is unambiguous.

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