Skip to main content
Glama

Get Law Commission Publication

get_law_commission_publication
Read-onlyIdempotent

Fetch one Law Commission of England & Wales publication (a consultation paper, report, summary or terms-of-reference) by its id (from search_law_commission_publications) or its lawcom.gov.uk link. Returns the law-reform project it belongs to and links to any attached PDF documents, the actual report text is the PDF; the WordPress record itself typically carries only a project link, not report prose.

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": {
      "id": 4941
    },
    "name": "get_law_commission_publication"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoPublication id, from search_law_commission_publications.
linkNoA lawcom.gov.uk/publication/... link, as an alternative to id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description does add real value beyond them: it discloses the return shape (parent project plus links to attached PDFs) and a non-obvious caveat that the WordPress record carries only a project link, not report prose. It does not say what happens on a missing/invalid id or when neither parameter is supplied.

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?

Front-loaded with the action and selector, then the return expectations and the key caveat about PDFs. Dense and mostly waste-free, though the final clause about WordPress prose is slightly convoluted in its phrasing.

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?

No output schema exists, so the description must characterize returns, and it does: the law-reform project and PDF links. It also warns that report text lives in the PDF rather than the record. The remaining gap is edge-case behavior when neither id nor link is provided (0 required parameters).

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 coverage is 100% and both properties already document the id source and the link alternative, so the schema does the heavy lifting. The description's only marginal addition is reinforcing that a link is an alternative to id, which the schema already states. Baseline 3 applies.

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?

A specific verb ("Fetch one") plus a precisely scoped resource (Law Commission of England & Wales publication), enumerating the record types returned and explicitly naming the sibling tool that supplies the id. An agent can distinguish this from search_law_commission_publications without opening either schema.

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

Usage Guidelines4/5

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

Establishes the intended workflow by stating the id comes "from search_law_commission_publications" and that a lawcom.gov.uk link works as an alternative. No explicit when-not-to-use case or exclusion, but the retrieval context is clear.

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.