Skip to main content
Glama

List the checks

list_checks
Read-only

List the 60 checks of rubric v0.9.1 across 5 dimensions, each with its kind, module, dimension, and rationale. A scored check also has a part, a tier and a weight. An unscored check earns 0 points.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real content by describing each returned item (kind, module, dimension, rationale) and the scored vs. unscored semantics ('unscored check earns 0 points'). It stops short of saying whether the rubric version is fixed or whether results are paginated/ordered, but for a no-arg read this is solid.

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?

Three short sentences, front-loaded with the count and rubric version, then item shape, then the scoring rule. No filler and nothing that repeats the title verbatim.

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 input parameters and no output schema, the description carries the return-value burden and mostly discharges it by enumerating the fields present on a check. A small gap remains on ordering, stability of the 60-check set, and what the agent should do with the rationale text.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The brief notes about item fields are return-shape rather than parameter information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb (list) plus resource (the 60 checks of rubric v0.9.1) and scope (5 dimensions), so the agent knows exactly what it enumerates. It doesn't name or contrast with the siblings get_report/get_score/scan_site, but the intent is unambiguous against them.

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

Usage Guidelines3/5

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

Usage is only implied: you call it to enumerate the rubric's checks. There is no explicit when-to-use statement, no exclusion such as 'call get_score to compute a score instead', and no note that this is a static reference listing rather than per-site data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.