National Digital

Read a National Digital page

fetch

Read-onlyIdempotent

Read one published National Digital page as clean Markdown, given an id from search (the page's site path, e.g. /platform-engineering/) or its full URL. Returns the page's text with its title, canonical url and last-modified date. Long pages are returned in parts; pass the returned nextOffset as offset to read the next part.

Input Schema

Name	Required	Description	Default
`id`	Yes	A page id from search (its site path, e.g. /about/) or the page URL.
`offset`	No	Character offset to read from; pass nextOffset from the previous part.

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`title`	Yes
`metadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026
- removedOutput schema / properties / metadata / properties / nextOffset / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / metadata / properties / nextOffset / type
```
Added value: +[
+  "number",
+  "null"
+]
```
First observedOct 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: content is returned as Markdown with title, canonical url and last-modified, and long pages are chunked with a nextOffset/offset continuation contract. It does not mention error cases (e.g. page not found or unpublished), which keeps it at 4.

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 sentences, front-loaded with the core action, then the return shape, then the pagination loop. No filler or redundancy; each sentence carries actionable information.

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?

Covers the inputs, the source of ids, the return payload, and the pagination continuation rule; an output schema exists so return values needn't be spelled out further. For a two-parameter read tool, nothing an agent needs in order to call it correctly is missing.

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% and both parameters are documented in the schema, including the offset/nextOffset relationship and the id example. The description restates rather than extends that: it gives the same site-path-vs-URL distinction and the same offset chaining rule, adding no new syntax or edge-case meaning.

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 (read) and resource (one published National Digital page) plus output format (clean Markdown), and distinguishes itself from the sibling `search` by noting the id comes from search. An agent can identify the tool without opening the 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?

Explains that the id comes from `search` and that either a site path (/platform-engineering/) or a full URL is acceptable, which implies the intended workflow (search first, then fetch). It does not state explicit exclusions or what to do if the id is unknown, so it stops short of full when/when-not guidance.

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

All National Digital tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?