Skip to main content
Glama
Sign In
UK Legal Research MCP Server

UK Legal Research MCP Server

by paulieb89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Read Resource

read_resource
Read-onlyIdempotent

Retrieve content from registered judgment://, legislation://, hansard://, or server:// URIs returned by this server; use it to access primary-source legal material, not https:// web URLs.

Instructions

Read a registered server resource URI, not an ordinary web URL.

USE WHEN you have a judgment://, legislation://, hansard://, or server:// URI returned by this server. Do not use for https:// URLs; use the source-specific tool instead (for a canonical GOV.UK HMRC internal-manual URL, call hmrc_get_manual_page).

Returns the resource content as a string. Binary content is base64-encoded.

AFTER calling, use the returned primary-source content and URI in citations; if the URI is rejected, follow the named source-specific tool rather than treating the URL as retrieved evidence.

Source: registered UK Legal MCP resource providers.

Input Schema

NameRequiredDescriptionDefault
uriYesA server resource URI such as judgment://..., legislation://..., hansard://..., or server://about

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.1
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. Changed1 schema field changedv0.8.0
    • changedInput schema / properties / uri / description
      Previous value: -"The URI of the resource to read"New value: +"A server resource URI such as judgment://..., legislation://..., hansard://..., or server://about"
  3. Changed1 schema field changedv0.6.1
    • addedOutput schema / description
      Added value: +"Generic wrapper for non-object return types."
  4. Addedv0.5.1
  5. Removed
  6. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description adds the genuinely non-obvious behavior that rejected URIs must not be treated as retrieved evidence, plus the encoding rule for binary content. The return-format sentence is partly redundant with the output schema, which keeps this from 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?

Short imperative sentences grouped under USE WHEN and AFTER headers make it front-loaded and scannable, with no wasted clauses. The trailing "Source: registered UK Legal MCP resource providers" line is metadata padding rather than actionable instruction.

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 single-parameter read tool with full annotation coverage and an output schema, the description supplies everything needed: what qualifies, what does not, which sibling to use instead, and how to treat failures. No gap remains that would cause a misinvocation.

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 the single uri parameter is already documented with the same scheme examples, so the description adds no new syntax, formatting, or validation meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

"Read a registered server resource URI, not an ordinary web URL" states a specific verb and resource and immediately draws the boundary that separates it from generic URL fetching and from the many source-specific siblings such as hmrc_get_manual_page or legislation_get_section. An agent can place this tool correctly 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?

The USE WHEN block enumerates the exact URI families (judgment://, legislation://, hansard://, server://) that qualify, and explicitly excludes https:// URLs while naming the concrete alternative to call instead (hmrc_get_manual_page). The AFTER block covers the fallback path when a URI is rejected, so both the positive and negative routing conditions are stated.

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

Deploy Server

Other Tools