UK Source Intelligence

by dev.workers.mazdamen.uk-source-intelligence-mcp

fixed_monitored_pages

Read-only

FREE, NO KEY: List the nine GOV.UK pages currently on the fixed monitoring schedule and their actual monitoring/database status. A first snapshot is a baseline, NOT evidence that any change has occurred. For observed wording changes use get_govuk_change_brief; for live current text use preview_source_evidence.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Adds real context beyond readOnlyHint=true: 'FREE, NO KEY' discloses the auth requirement, and the baseline warning prevents a costly misinterpretation of returned data. It does not spell out the exact response shape, but with no output schema the 'nine pages + monitoring/database status' phrasing is close to sufficient.

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 short sentences: cost/auth qualifier front-loaded, then what is returned, then the misinterpretation warning, then sibling routing. Each sentence carries distinct information with no repetition.

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?

A zero-parameter read tool with a single readOnly annotation needs exactly this: what it returns, why the result may look like 'no change', the auth cost, and where to go for adjacent needs. Nothing an agent needs 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for 0 params applies. The description correctly reflects a no-argument list operation with no implied filtering options.

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 ('List') and a precisely scoped resource ('the nine GOV.UK pages currently on the fixed monitoring schedule') plus the returned status fields. The word 'fixed' implicitly separates it from user-configured watches like list_my_watches, and the tool is identifiable 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 Guidelines5/5

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

Explicitly routes the agent: get_govuk_change_brief for observed wording changes, preview_source_evidence for live current text. It also pre-empts the most likely misuse by stating a first snapshot is a baseline, not evidence of a change.

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

All UK Source Intelligence 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?