Skip to main content
Glama
Sign In

Checkbox

by site.checkbox
OverviewDiscussionsAdmin

List compliance findings

list_findings
Read-onlyIdempotent

Findings (one per legal check per site) ordered by urgency: failing first, then by severity, each with citations. Filter by site, status (fail, needs_review, pass, not_applicable) and state (open, acknowledged, resolved, accepted_risk). Default: every open finding of every status. Use get_finding for the fix of one.

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_findings"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoOnly this site (site_…).
limitNoHow many to return (1-100, default 10).
stateNoDefault open.
statusNoDefault: all statuses.
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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuine behavioral value with the urgency ordering (failing first, then severity) and the fact that each item carries citations. It says nothing about page size vs. total results or what has_more/has_more-style pagination looks like, leaving the result envelope implicit.

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?

Three tight sentences with the ordering and default behavior front-loaded and no filler. The opening is a noun fragment ('Findings...') rather than a verb phrase, which is slightly terse but still parses immediately in context.

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 read-only, zero-required-parameter list tool with full schema coverage and annotations that carry the safety profile, the description supplies what is missing: item granularity, sort order, citations, and default filter scope. No output schema exists, yet the description gives enough about item shape and ordering for correct invocation.

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 every parameter including the pagination cursor is already documented in structured form. The description restates the enum values and defaults that the schema already declares, adding little beyond them. Baseline 3 applies when the schema is doing 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 a specific resource (compliance findings), its granularity (one per legal check per site), its ordering (failing first, then by severity) and its payload (citations). It also explicitly distinguishes itself from get_finding, so an agent can pick between the list and the single-item view without opening either 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?

Names the filter dimensions (site, status, state), states the default behavior ('every open finding of every status'), and routes the agent to get_finding 'for the fix of one.' That is explicit conditional guidance. It lacks a clear when-not-to-use statement or any mention of related list tools such as list_due_notices, which keeps it below a 5.

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