Skip to main content
Glama

Gov Uk Content

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Content

content
Read-onlyIdempotent

Fetch the full rendered content and metadata of any single GOV.UK page from its base_path — guidance, a policy paper, an organisation page, a departmental manual or one section of one. Returns title, description, body, publication and last-updated timestamps, and the page's links. Use gov_uk_search or hmrc_manual_search first when you do not already know the base_path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "base_path": "/guidance/apply-for-a-uk-visa"
+  },
+  {
+    "base_path": "/benefits/child-benefit"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Content retrieved from GOV.UK API for a given base_path",
+  "type": "object"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, openWorld, and non-destructive behavior, so the bar is lower. The description adds meaningful context by saying it returns full rendered content plus title, description, body, timestamps, and links. It does not discuss failure modes or rate limits, but the output schema and annotations cover the main safety profile.

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 with no wasted wording: purpose, return contents, and usage alternative are front-loaded. Every clause contributes, and the search-first instruction is placed at the end as a natural follow-on.

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?

For a simple one-parameter, read-only tool with an output schema and rich annotations, the description provides everything an agent needs: scope, return coverage, and when to use search instead. The reference to gov_uk_search (not present in the sibling list) is minor and does not affect completeness because hmrc_manual_search is listed and the intent is clear.

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 0%, so the description must carry the parameter meaning. It does by defining base_path as the path to a single GOV.UK page, and the schema examples reinforce the leading-slash format. It stops short of documenting edge cases like URL-encoding or invalid paths, but this is sufficient for a single-parameter tool.

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 opens with a specific verb and resource: 'Fetch the full rendered content and metadata of any single GOV.UK page from its base_path.' It enumerates page types and explicitly scopes to one page, which distinguishes it from search/list siblings.

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?

It states a clear routing rule: 'Use gov_uk_search or hmrc_manual_search first when you do not already know the base_path.' This tells an agent exactly when to prefer a sibling, leaving no doubt about the prerequisite for calling content.

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

All Gov Uk Content toolsInspect
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