UK Source Intelligence

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

preview_source_evidence

Read-only

FREE, NO KEY, NO SIGNUP: Run a real live demonstration against the official GOV.UK VAT rates source. Returns its official URL, government content identifier, source timestamp, fetched text excerpt, a SHA-256 digest and a quote-presence check. Uses one fixed public example; it does NOT claim historical changes or replace UKSI monitored snapshots. For historical change tasks prefer get_govuk_change_brief; this tool only checks current VAT text.

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

Input Schema

Name	Required	Description	Default
`quote`	No	Optional quotation to check in the GOV.UK VAT rates page, max 200 characters. If omitted, checks a built-in example.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

readOnlyHint=true is already declared, and the description adds real value on top: no key/signup required, a fixed public example is used, the returned evidence fields are named, and its epistemic limits are stated ('does NOT claim historical changes'). It stops short of covering failure behavior, rate limits, or how the digest/quote check result should be interpreted, so a 4 rather than a 5.

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 with the strongest fact (free, no key, no signup) and then the behavior; sentences are dense with information. Minor redundancy in restating the no-historical-changes limit twice ('does NOT claim historical changes' / 'only checks current VAT text').

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?

There is no output schema, but the description enumerates the return fields in their place and scopes the tool's claims, which is enough to call it correctly. Missing only edge-case behavior (what a failed fetch or a digest mismatch means).

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 single optional 'quote' parameter is fully documented there (max 200 chars, built-in example fallback). The description adds only a light gloss ('a quote-presence check' and 'uses one fixed public example'), so baseline 3 applies.

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+resource: run a live demonstration against the official GOV.UK VAT rates source, and enumerates exactly what it returns (URL, content identifier, timestamp, excerpt, SHA-256 digest, quote check). It also explicitly distinguishes itself from get_govuk_change_brief, so the agent can route without opening schemas.

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?

Explicit exclusions and an alternative are present: it does not claim historical changes, does not replace UKSI monitored snapshots, and historical tasks should use get_govuk_change_brief. The positive trigger (a free/low-commitment live sanity check of current VAT text) is clear but slightly implicit compared to the negative cases.

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?