Skip to main content
Glama
Sign In

Checkbox

by site.checkbox
OverviewDiscussionsAdmin

List sites

list_sites
Read-onlyIdempotent

The account's sites in the current mode (test keys see only test-mode sites), newest first, each with its compliance status label. Use it to find a site id.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (1-100, default 10).
archivedNotrue lists only archived sites.
starting_afterNoPagination cursor: the last id of the previous page (when has_more was true).

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 readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: that results are mode-scoped by key type, that ordering is newest-first, and that a compliance status label is attached to each site. It stops short of explaining what happens across pagination boundaries, though the schema's starting_after parameter covers that.

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 tight sentences with zero filler. Scope and ordering come first, followed immediately by the concrete use case, which is the right front-loading for a list tool.

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 does the necessary work of saying what each returned item contains (a compliance status label) and how results are ordered. The remaining gap is minor: pagination behavior is only inferable from the schema's starting_after description rather than stated in the description itself.

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%, with limit, archived, and starting_after all documented inline, so the baseline is 3. The description adds no parameter-level detail beyond the implied mode filtering, which is not a parameter at all.

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?

The description names a specific verb and resource (listing the account's sites), states the scoping rule (current mode, test keys see test-mode sites), the ordering (newest first), and the payload content (compliance status label per site). An agent can distinguish this from create_site, update_site, and get_site_status 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 Guidelines4/5

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

"Use it to find a site id" gives a concrete selection criterion for the tool. It does not name an alternative for related needs, such as get_site_status when a specific site's status is already known, so the routing guidance is clear but not exhaustive.

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