Skip to main content
Glama

UK company & compliance data

UK Legislation: Search legislation

uk-legislation__search
Read-onlyIdempotent

Find Acts and instruments by title words or full text, optionally by type and year. Free within the daily allowance, then $0.002 USDC per call via x402.

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": "uk-legislation__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResults page (20 per page)
textNoWords anywhere in the text
typeNoType code (see types)
yearNoYear
titleNoWords in the title

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavioral context the annotations lack: a cost model (free within a daily allowance, then $0.002 USDC per call via x402). It does not discuss result limits or pagination behavior, so it stops short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with what the tool does followed by the pricing caveat. No filler and nothing redundant.

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?

An output schema exists, so return values need not be explained. Combined with full schema coverage and annotation-backed safety, the description covers purpose and cost adequately; only the lack of routing guidance against sibling tools is a meaningful gap.

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 all five parameters are already documented in the schema. The description's mention of title/full-text/type/year mirrors the schema without adding syntax or format detail, so the baseline 3 applies.

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 pairs a specific verb ('Find') with a specific resource ('Acts and instruments') and states the searchable facets (title words or full text, type, year). It is clearly a search tool, but it never names or differentiates itself from siblings like uk-legislation__latest, uk-legislation__item, or uk-legislation__changes.

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

Usage Guidelines2/5

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

It lists what can be searched but gives no when-to-use context and no alternatives. An agent cannot tell from the description whether to reach for this tool or uk-legislation__latest/uk-legislation__item for a given need.

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