Skip to main content
Glama

BRAINIAC Regulatory Intelligence

Get UK legislation details

regulatory-intelligence_uk-details
Read-onlyIdempotent

Retrieve UK legislation details, publication dates, commencement information, and amendment metadata from legislation.gov.uk XML data. Price $0.05 USDC. POST /api/v1/regulatory-intelligence/uk/details. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "documentId": "<documentId>"
    },
    "name": "regulatory-intelligence_uk-details"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentIdYesdocumentId, string, length 1 to 200. Required.

Output Schema

NameRequiredDescriptionDefault
foundNofound. Boolean.
sourceNosource. Object.
documentIdNodocumentId. String.
legislationNolegislation. Object.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuinely new operational context: the exact cost ($0.05 USDC), the POST route, and that an unpaid call returns x402 payment terms without executing — important for an agent to avoid false success reads.

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?

Three short sentences, front-loaded with the capability before the commercial and endpoint details. No filler, though the price and payment sentence could be tightened into one line without loss.

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?

With an output schema present, return values need not be described, and the single required parameter plus payment mechanics are covered. What remains missing is routing guidance relative to the sibling search tool, which is the only material gap for a tool this simple.

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?

There is a single required parameter with 100% schema description coverage, so the schema already fully documents documentId. The description adds no further meaning about its format, origin, or where to obtain it, which is the expected baseline-3 outcome 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Retrieve UK legislation details') and enumerates the payload (publication dates, commencement information, amendment metadata) plus the source (legislation.gov.uk XML). The UK qualifier implicitly separates it from the US sibling, though it never names the alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: the required documentId suggests this is the follow-up to a search call, and the UK source narrows the domain. There is no explicit statement of when to choose this over regulatory-intelligence_uk-search or the US counterpart, and no stated prerequisites or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources