Website Spec

Get one spec page

get_topic

Read-onlyIdempotent

Read-only. Fetch the full canonical Markdown for a single spec page by its slug: YAML frontmatter (title, status, category, sources, related slugs) plus the rendered body. Use this once you have a slug from search or list_topics. If you only have keywords, call search first.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Kebab-case slug, as listed by `list_topics` or `search`. Matched case-insensitively, with close-match suggestions on miss. Examples: `content-security-policy`, `meta-robots`, `llms-txt`.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Canonical HTML URL.
`slug`	Yes	Kebab-case identifier of this page.
`mdUrl`	Yes	Raw Markdown URL.
`title`	Yes	Human-readable page title.
`status`	Yes	Spec status tier: `required`, `recommended`, `optional`, or `avoid`.
`sources`	No	Primary-source citations for this page.
`summary`	Yes	One-sentence summary of the topic.
`updated`	No	ISO 8601 timestamp of the last content update, or null.
`category`	Yes	Top-level category this topic belongs to.
`markdown`	Yes	The full page as Markdown with YAML frontmatter.
`relatedSlugs`	No	Slugs of related topics; each can be passed to `get_topic`.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed9 schema fields changedJun 9, 2026
- addedOutput schema / properties / category / description
```
Added value: +"Top-level category this topic belongs to."
```
- addedOutput schema / properties / relatedSlugs / description
```
Added value: +"Slugs of related topics; each can be passed to `get_topic`."
```
- addedOutput schema / properties / slug / description
```
Added value: +"Kebab-case identifier of this page."
```
- addedOutput schema / properties / sources / items / properties / publisher / description
```
Added value: +"Publishing body (e.g. WHATWG, W3C, IETF), if known."
```
- addedOutput schema / properties / sources / items / properties / title / description
```
Added value: +"Title of the cited source."
```
- addedOutput schema / properties / sources / items / properties / url / description
```
Added value: +"URL of the cited source."
```
- addedOutput schema / properties / status / description
```
Added value: +"Spec status tier: `required`, `recommended`, `optional`, or `avoid`."
```
- addedOutput schema / properties / summary / description
```
Added value: +"One-sentence summary of the topic."
```
- addedOutput schema / properties / title / description
```
Added value: +"Human-readable page title."
```
Changed1 schema field changedJun 8, 2026
- addedInput schema / properties / slug / minLength
```
Added value: +1
```

Changed2 schema fields changedJun 4, 2026

changedInput schema / properties / slug / description

Previous value: -"Kebab-case slug, as listed by `list_topics` or `search`. Examples: `content-security-policy`, `meta-robots`, `llms-txt`."New value: +"Kebab-case slug, as listed by `list_topics` or `search`. Matched case-insensitively, with close-match suggestions on miss. Examples: `content-security-policy`, `meta-robots`, `llms-txt`."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "category": {
+      "enum": [
+        "foundations",
+        "seo",
+        "accessibility",
+        "security",
+        "well-known",
+        "agent-readiness",
+        "performance",
+        "privacy",
+        "resilience",
+        "i18n"
+      ],
+      "type": "string"
+    },
+    "markdown": {
+      "description": "The full page as Markdown with YAML frontmatter.",
+      "type": "string"
+    },
+    "mdUrl": {
+      "description": "Raw Markdown URL.",
+      "type": "string"
+    },
+    "relatedSlugs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "sources": {
+      "description": "Primary-source citations for this page.",
+      "items": {
+        "properties": {
+          "publisher": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "enum": [
+        "required",
+        "recommended",
+        "optional",
+        "avoid"
+      ],
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "updated": {
+      "description": "ISO 8601 timestamp of the last content update, or null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "Canonical HTML URL.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "title",
+    "category",
+    "status",
+    "url",
+    "mdUrl",
+    "summary",
+    "markdown"
+  ],
+  "type": "object"
+}

First observedJun 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds value by confirming it is 'Read-only' and detailing the return structure: 'YAML frontmatter (title, status, category, sources, related slugs) plus the rendered body.' It also mentions close-match suggestions on miss, providing behavioral context beyond annotations.

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 two concise sentences, front-loaded with 'Read-only.' and the core purpose. Every sentence adds value without redundancy.

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?

Given the tool has one parameter, full schema coverage, and an output schema (implied), the description adequately covers the return structure and prerequisite usage. It lacks details on error scenarios but is sufficient for a simple fetch operation.

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 coverage is 100%, and the input schema already thoroughly describes the 'slug' parameter with examples and behavior (case-insensitive, close-match suggestions). The description does not add significant additional meaning beyond restating that it fetches by slug.

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 'Fetch the full canonical Markdown for a single spec page by its slug'. It specifies the verb 'Fetch', the resource 'canonical Markdown for a single spec page', and the input parameter 'slug'. It also distinguishes itself from sibling tools like 'search' and 'list_topics' by noting the prerequisite of having a slug from those tools.

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 provides explicit guidance: 'Use this once you have a slug from `search` or `list_topics`.' and 'If you only have keywords, call `search` first.' This clearly communicates when to use this tool versus alternatives.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: get_categories for categories, get_changes for history, get_checklist for checklists, get_topic for single page, list_topics for listing, and search for full-text. There is no overlap.

Naming Consistency4/5

Most tools follow 'get_' pattern (get_categories, get_changes, get_checklist, get_topic), but list_topics and search break the pattern. However, all names are intuitive and consistent in using lowercase with underscores.

Tool Count5/5

With 6 tools covering categories, search, listing, details, checklist, and changes, the count is well-suited for a specification reference. Each tool serves a clear need without excess.

Completeness5/5

The tool set covers all read operations needed for a specification: discovery (categories, search), browsing (list_topics, get_checklist), deep dive (get_topic), and change tracking (get_changes). No obvious gaps for its intended use.

Resources

Need Help?