Global law

List provisions

list_provisions

Read-onlyIdempotent

Browse a corpus: the provision files under a corpus or folder (for example united-states/federal/usc/title-11), with headings, as in force on a date. For a folder of acts or instruments, by_folder gives one row each with its title and last change; a partial name lists the folders that start with it (malta/national/acts/sl/586. for every instrument made under Cap. 586).

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": {
      "path": "<path>"
    },
    "name": "list_provisions"
  }
}

Input Schema

Name	Required	Description
`date`	No	An in-force date, YYYY-MM-DD, or "today". Defaults to today.
`path`	Yes	A corpus, a folder inside one, or the start of a folder name.
`offset`	No	Rows to skip: the next_offset the answer before gave in "page" (default 0).
`by_folder`	No	One row per sub-folder (an act or instrument) with its title and last change.
`max_results`	No	At most this many (of folders, at most 100) (default 200, at most 2000).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

changedInput schema / properties / max_results / description

Previous value: -"At most this many (default 200)."New value: +"At most this many (of folders, at most 100) (default 200, at most 2000)."

addedInput schema / properties / offset

Added value: +{
+  "description": "Rows to skip: the next_offset the answer before gave in \"page\" (default 0).",
+  "type": "integer"
+}

First observedNov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds useful behavioral detail about what is returned in each mode: provision files with headings as in force on a date, or one folder row with title and last change.

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 description is compact and front-loads the core browsing behavior. The second sentence is somewhat dense with two modes and examples, but it remains purposeful rather than 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?

Given the output schema, annotations, and full schema description coverage, the description is largely complete. It covers the main modes and in-force date semantics; pagination and result limits are adequately handled by the schema.

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 baseline is 3. The description provides examples and clarifies partial-name matching and by_folder behavior, but much of that meaning is already present in the schema descriptions.

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 states a specific verb and resource: browsing provision files under a corpus or folder, with headings, as in force on a date. It clearly conveys the listing/browsing scope, though it does not explicitly name sibling alternatives to differentiate itself from search-oriented tools.

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?

It explains the main usage context and distinguishes two modes: normal corpus/folder browsing and by_folder listing for folders of acts or instruments. It also explains partial-name lookup, but gives no explicit when-not-to-use guidance or named alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Global law tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.