Skip to main content
Glama

BRAINIAC Regulatory Intelligence

Search UK legislation

regulatory-intelligence_uk-search
Read-onlyIdempotent

Search UK legislation by keyword, document type, year, and jurisdiction. Note: legislation.gov.uk does not provide a public JSON search API. This endpoint has limited functionality. Price $0.05 USDC. POST /api/v1/regulatory-intelligence/uk/search. 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": {
      "query": "<query>"
    },
    "name": "regulatory-intelligence_uk-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoyear, integer, from 1000 to 3000. Optional.
limitNolimit, integer, from 1 to 50. Required.
queryYesquery, string, length 1 to 200. Required.
jurisdictionNojurisdiction, string, length 0 to 50. Optional.
legislationTypeNolegislationType, string, length 0 to 50. Optional.

Output Schema

NameRequiredDescriptionDefault
queryNoquery. String.
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
resultCountNoresultCount. Number.
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?

The description adds materially beyond the annotations, which already declare readOnly/idempotent/non-destructive behavior. It discloses cost ($0.05 USDC), that an unpaid call returns x402 payment terms without executing, and that upstream legislation.gov.uk has no public JSON search API with limited functionality — critical operational facts an agent cannot get from structured fields.

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?

The purpose sentence is front-loaded and the operational notes follow in descending priority (limitation, price, endpoint, payment gating). The trailing fragments (price, path, x402 note) are terse but each carries unique information, so there is little waste.

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 the description need not explain return values, and annotations cover the safety profile, so the remaining burden is operational context — which the payment gating and upstream API limitation address well. The only real gap is guidance on how this relates to the details/other-jurisdiction siblings.

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%, so the schema already documents all five parameters with types and bounds. The description restates the facet names in prose but adds no syntax, format, matching behavior, or default guidance beyond what the schema provides, making 3 the appropriate baseline.

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?

States a specific verb and resource ('Search UK legislation') and enumerates the searchable facets (keyword, document type, year, jurisdiction), which is enough to separate it from sibling tools like uk-details and us-search by subject matter. It stops short of explicitly contrasting itself with those siblings, so it lands at 4 rather than 5.

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 context is only implied: it is a UK-legislation keyword search, so an agent can infer it should be used before drilling into a details endpoint. There is no explicit when-to-use or when-not-to-use statement, and the warning that 'this endpoint has limited functionality' gives no alternative or threshold for switching tools.

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