Skip to main content
Glama

Law details

law_details
Read-onlyIdempotent

The full record of a law's change: its commit message with every trailer (enacted, in force, published, sources, scope), the provisions it changed, and what it did to each one's words (a word diff, or "layout only", or "text moved between provisions"). One call answers "what did this law change"; no need to compare each provision.

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": "law_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawNoThe law as it appears as author, for example "Pub. L. 117-151", "36. Änderung", "S.I. 2020/471".
commitNoOr a corpus commit hash, for example from provision_history.
jurisdictionNoOptional jurisdiction: a country by its name in English or its own language ("germany", "Deutschland", "UK") or its ISO code ("de"), or a path prefix, for example "germany", "united-states/federal" or "united-kingdom/uk/legislation/uksi".
include_diffsNoWhat the change did to each provision (default true; up to 60 provisions).
max_message_charsNoCut each commit message at this many characters (default 3000, at least 500, at most 50000).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"Optional jurisdiction prefix, for example \"germany\", \"united-states/federal\" or \"united-kingdom/uk/legislation/uksi\"."New value: +"Optional jurisdiction: a country by its name in English or its own language (\"germany\", \"Deutschland\", \"UK\") or its ISO code (\"de\"), or a path prefix, for example \"germany\", \"united-states/federal\" or \"united-kingdom/uk/legislation/uksi\"."
  2. Changed3 schema fields changed
    • removedInput schema / properties / corpus
      Removed value: -{
      -  "description": "Optional jurisdiction prefix, for example \"germany\", \"united-states/federal\" or \"united-kingdom/uk/legislation/uksi\".",
      -  "type": "string"
      -}
    • addedInput schema / properties / jurisdiction
      Added value: +{
      +  "description": "Optional jurisdiction prefix, for example \"germany\", \"united-states/federal\" or \"united-kingdom/uk/legislation/uksi\".",
      +  "type": "string"
      +}
    • changedInput schema / properties / max_message_chars / description
      Previous value: -"Cut each commit message at this many characters (default 3000)."New value: +"Cut each commit message at this many characters (default 3000, at least 500, at most 50000)."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds real value beyond that by disclosing the payload's shape and the possible diff outcomes ('a word diff', 'layout only', 'text moved between provisions'), which an agent cannot infer from annotations.

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?

Two sentences that are front-loaded with the core answer and end with the decision rule. The long parenthetical enumerating trailers and diff types is dense but each item carries information; no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering the safety profile, an output schema covering return shape, and full parameter documentation, the description only needs to explain what the record conceptually contains — which it does. Nothing needed to call it correctly is missing.

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 explains law, commit, jurisdiction, include_diffs and max_message_chars with examples and defaults. The description adds only indirect meaning (the 60-provision effect of include_diffs via 'what it did to each one's words') and does not clarify the law-versus-commit alternative itself, so 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?

States a specific resource precisely: the full record of a law's change, enumerating the commit message with trailers, the changed provisions, and the per-provision word-level outcome. It is clearly not a plain text read or a search, but it does not explicitly contrast itself with the closely named sibling read_law, which an agent could confuse with 'law_details'.

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?

'One call answers "what did this law change"; no need to compare each provision' gives a concrete use case and steers the agent away from per-provision comparison. It stops short of naming the alternative tool (e.g. changes_between, provision_history) or stating when this is the wrong choice.

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.