Skip to main content
Glama

List Law Commission Projects

list_law_commission_projects
Read-onlyIdempotent

List law-reform projects run by the Law Commission of England & Wales (lawcom.gov.uk/project), the workstreams under which its consultation papers and reports are published, e.g. "Commercial leasehold" or "Consumer class actions". Optionally narrow by status. Welsh-language duplicates are filtered out, one row per project.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 12,
      "status": "current"
    },
    "name": "list_law_commission_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoProjects to return, 1-50 (default 20).
statusNoFilter by project status: "current", "completed", "upcoming", or "other". Omit to list all statuses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive open-world read, so safety is covered. The description adds real behavior beyond that: Welsh-language duplicates are filtered out and results are one row per project, which tells the agent the cardinality and dedup semantics of the output. It stops short of describing ordering or pagination behavior beyond the limit parameter.

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?

Three sentences, all front-loaded: identity and source first, optional filter second, output-shape caveat last. Every clause carries information an agent can act on, with no filler or repetition of the schema.

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?

For a read-only, two-parameter listing tool with full schema coverage and no output schema, the description covers purpose, scope, optional filtering, deduplication, and row granularity. The one remaining gap is that, absent an output schema, it does not say what fields a project row contains, forcing the agent to discover the return shape by calling it.

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 both limit (range and default) and status (the four accepted values) are fully documented in the schema, establishing a baseline of 3. The description only restates that status is an optional narrowing filter and adds no format, matching, or edge-case semantics beyond the schema.

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: list law-reform projects run by the Law Commission of England & Wales, with concrete example workstream names ("Commercial leasehold", "Consumer class actions") and the source domain. It implicitly separates projects from the publication tools by describing projects as the workstreams under which papers/reports are published, but it never names search_law_commission_publications or get_law_commission_publication to make the routing explicit.

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?

"Optionally narrow by status" tells the agent that status filtering is optional and that omitting it lists everything, which is genuine usage guidance. There is no statement of when this list tool should be preferred over the sibling search/get publication tools, so the choice between them is left to inference.

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.