Website Spec

Get an audit checklist

get_checklist

Read-onlyIdempotent

Read-only. Return a Markdown checklist of spec items grouped by category, optionally filtered by category and/or status. Built for site audits — each item is a tickable line with status and canonical URL. Returns all statuses unless status is passed. No side effects; items are grouped by category in canonical order and the output is deterministic. Use list_topics instead when you want a flat list rather than grouped checkboxes, or the audit_url prompt to drive an actual audit of a target URL.

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

Input Schema

Name	Required	Description	Default
`status`	No	Filter by spec status tier. `required` = the web-platform contract breaks or a clear class of users is harmed without it. `recommended` = a modern site should do it. `optional` = context-dependent. `avoid` = outdated, harmful, or superseded. Omit to include all four tiers. Example: `required`.
`category`	No	Filter to a single top-level category. Call `get_categories` for the list with descriptions and topic counts. Omit to include all ten categories. Example: `seo`.

Output Schema

Name	Required	Description
`total`	Yes	Total checklist items across all groups.
`filters`	Yes	The filters that were applied (omitted keys mean no filter).
`categories`	Yes	Checklist groups in canonical category order, each holding its items.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedJun 9, 2026
- addedOutput schema / properties / categories / description
```
Added value: +"Checklist groups in canonical category order, each holding its items."
```
- addedOutput schema / properties / categories / items / properties / items / description
```
Added value: +"Checklist entries in this category, in canonical page order."
```
- addedOutput schema / properties / categories / items / properties / items / items / properties / slug / description
```
Added value: +"Kebab-case identifier; pass to `get_topic`."
```
- addedOutput schema / properties / categories / items / properties / items / items / properties / status / description
```
Added value: +"Spec status tier: `required`, `recommended`, `optional`, or `avoid`."
```
- addedOutput schema / properties / categories / items / properties / items / items / properties / summary / description
```
Added value: +"One-sentence summary of the item."
```
- addedOutput schema / properties / categories / items / properties / items / items / properties / title / description
```
Added value: +"Human-readable page title."
```
- addedOutput schema / properties / categories / items / properties / items / items / properties / url / description
```
Added value: +"Canonical HTML URL of the spec page."
```
- addedOutput schema / properties / categories / items / properties / slug / description
```
Added value: +"Kebab-case category identifier."
```
- addedOutput schema / properties / categories / items / properties / title / description
```
Added value: +"Human-readable category title."
```
- addedOutput schema / properties / filters / description
```
Added value: +"The filters that were applied (omitted keys mean no filter)."
```
- addedOutput schema / properties / filters / properties / category / description
```
Added value: +"The category filter that was applied, if any."
```
- addedOutput schema / properties / filters / properties / status / description
```
Added value: +"The status filter that was applied, if any."
```

Changed2 schema fields changedJun 8, 2026

changedInput schema / properties / category / description

Previous value: -"Filter to a single top-level category. Call `get_categories` for the list with descriptions and topic counts. Omit to include all ten categories."New value: +"Filter to a single top-level category. Call `get_categories` for the list with descriptions and topic counts. Omit to include all ten categories. Example: `seo`."

changedInput schema / properties / status / description

Previous value: -"Filter by spec status tier. `required` = the web-platform contract breaks or a clear class of users is harmed without it. `recommended` = a modern site should do it. `optional` = context-dependent. `avoid` = outdated, harmful, or superseded. Omit to include all four tiers."New value: +"Filter by spec status tier. `required` = the web-platform contract breaks or a clear class of users is harmed without it. `recommended` = a modern site should do it. `optional` = context-dependent. `avoid` = outdated, harmful, or superseded. Omit to include all four tiers. Example: `required`."

Changed3 schema fields changedJun 4, 2026

addedInput schema / properties / category / description

Added value: +"Filter to a single top-level category. Call `get_categories` for the list with descriptions and topic counts. Omit to include all ten categories."

addedInput schema / properties / status / description

Added value: +"Filter by spec status tier. `required` = the web-platform contract breaks or a clear class of users is harmed without it. `recommended` = a modern site should do it. `optional` = context-dependent. `avoid` = outdated, harmful, or superseded. Omit to include all four tiers."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "categories": {
+      "items": {
+        "properties": {
+          "items": {
+            "items": {
+              "properties": {
+                "slug": {
+                  "type": "string"
+                },
+                "status": {
+                  "enum": [
+                    "required",
+                    "recommended",
+                    "optional",
+                    "avoid"
+                  ],
+                  "type": "string"
+                },
+                "summary": {
+                  "type": "string"
+                },
+                "title": {
+                  "type": "string"
+                },
+                "url": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "slug",
+                "title",
+                "status",
+                "summary",
+                "url"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "items"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "filters": {
+      "properties": {
+        "category": {
+          "enum": [
+            "foundations",
+            "seo",
+            "accessibility",
+            "security",
+            "well-known",
+            "agent-readiness",
+            "performance",
+            "privacy",
+            "resilience",
+            "i18n"
+          ],
+          "type": "string"
+        },
+        "status": {
+          "enum": [
+            "required",
+            "recommended",
+            "optional",
+            "avoid"
+          ],
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "total": {
+      "description": "Total checklist items across all groups.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "filters",
+    "categories"
+  ],
+  "type": "object"
+}

First observedJun 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description adds value beyond annotations (readOnlyHint, idempotentHint) by stating no side effects, deterministic output, items grouped by category, and that all statuses are returned unless filtered. While annotations already indicate safety, the description enriches the behavioral model.

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?

The description is concise and front-loaded with 'Read-only.' Each sentence adds distinct value: purpose, filtering behavior, comparison with alternatives, and guarantee of no side effects. No wasted words.

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?

Given the presence of an output schema and moderate complexity, the description fully covers tool behavior: what it returns (Markdown checklist), grouping, filtering options, determinism, and related tools. It is complete for an AI agent to select and invoke correctly.

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?

Both parameters have full schema coverage with descriptions and enums. The description provides additional context on the meaning of status tiers and references 'get_categories' for category details. This reinforces but does not significantly add beyond the schema.

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 clearly states it returns a Markdown checklist of spec items grouped by category, optionally filtered by category and/or status. It specifies the tool is read-only and built for site audits. It distinguishes from siblings by referencing 'list_topics' for a flat list and the 'audit_url' prompt for driving an audit.

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?

The description explicitly provides when to use this tool versus alternatives: 'Use `list_topics` instead when you want a flat list rather than grouped checkboxes, or the `audit_url` prompt to drive an actual audit of a target URL.' It also clarifies that omitting status returns all statuses, guiding proper usage.

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

All Website Spec tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?