Website Spec

Website 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.

Input Schema

TableJSON 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

TableJSON 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.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the bar is lower, yet the description adds real context: the output is a Markdown checklist of tickable lines with status and canonical URL, grouped in canonical order, and the output is deterministic. That is genuine behavioral disclosure beyond the structured fields.

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-loaded and dense with useful routing information, and every sentence roughly earns its place. Minor redundancy: the opening "Read-only" and "No side effects" restate readOnlyHint, slightly inflating the length.

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?

With an output schema present, return values need not be explained, yet the description still clarifies output format and determinism. Combined with the filter defaults and sibling routing, nothing an agent needs to call this correctly is missing.

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?

Schema coverage is 100% with fully documented enums, so the baseline is 3. The description adds the default-filter semantics (all statuses returned when status is omitted) and reinforces the category grouping behavior, which is a modest but real increment over 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?

States a specific verb and resource ("Return a Markdown checklist of spec items grouped by category") and immediately names the sibling it is not (list_topics), so an agent can differentiate 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 Guidelines5/5

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

Explicitly routes the agent: use list_topics for a flat list instead of grouped checkboxes, and the audit_url prompt to drive an actual audit. It also states the default filtering behavior (all statuses unless status is passed), covering both when to use and how the filters change scope.

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

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

Need Help?