Checkbox

Create a site (write)

create_site

WRITE: registers a new subscription website for monitoring in the current mode. Confirm with the user before calling (it creates a monitored site; with a live key it starts scheduled scans once the account is activated). Prefer setup_checkbox for a new project (it also registers policies, the snippet and runs the first checks). Use create_site for an additional site. Only url is required. Returns the site with install details (snippet tag, inbound email). Next: install the snippet, then run_scan.

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": {
      "url": "<url>"
    },
    "name": "create_site"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Base URL of the business website, e.g. "https://acme.example".
`name`	No	Display name.
`facts`	No	Business facts that decide which requirements apply.
`platform`	No	Billing platform.
`checkout_url`	No	Page with the subscribe button (defaults to url).
`jurisdictions`	No	Jurisdictions to evaluate (empty = all US laws).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
First observedNov 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare write, non-idempotent, open-world, non-destructive, so the bar is lower; the description still adds real context by warning to confirm with the user and noting that with a live key scheduled scans begin once the account is activated. It does not discuss whether duplicate URLs are rejected or how the create fails, which keeps it short of 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?

Front-loads the WRITE marker and purpose, then the guidance, then the return and next step. Sentences earn their place, though the parenthetical about live keys is slightly cramped.

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?

For a 6-parameter write tool with a nested facts object and no output schema, it discloses the return value (site with snippet tag and inbound email) and the follow-up workflow. Combined with full schema coverage, an agent has everything needed to call it safely.

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 per-field descriptions for url, checkout_url, platform enum and facts, so the schema carries parameter meaning. The description adds only the 'only url is required' note, which merely restates the required array, so 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 a specific verb and resource ('registers a new subscription website for monitoring in the current mode'), and immediately distinguishes itself from setup_checkbox and (by implication) update_site. An agent can tell exactly what this creates without opening the 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 routing rules: prefer setup_checkbox for a new project because it also registers policies and the snippet, use create_site only for an additional site. It also supplies the post-call sequence (install the snippet, then run_scan), leaving nothing to inference.

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

All Checkbox tools Inspect

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.