Global law

What else changes

what_else_changes

Read-onlyIdempotent

Which provisions rely on, cite or use the definitions of this one, on a date: those that cite it, and those that use a term it defines (for example the provisions that use "debtor in possession"), with the definition's scope ("In this subchapter"). Use it before a text search when asked what depends on a provision or its definitions; a change to this provision can change what they mean.

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

Input Schema

Name	Required	Description
`date`	No	An in-force date, YYYY-MM-DD, or "today". Defaults to today.
`path`	Yes	A provision file, for example united-states/federal/usc/title-11/1182.md, from find_provision.
`offset`	No	Rows to skip in each group: the next_offset the answer before gave in "page" (default 0).
`max_results`	No	Provisions per group (default 40, at most 500).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 10, 2026

changedInput schema / properties / max_results / description

Previous value: -"Provisions per group (default 40)."New value: +"Provisions per group (default 40, at most 500)."

addedInput schema / properties / offset

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

changedInput schema / properties / path / description

Previous value: -"A provision file, for example united-states/federal/usc/title-11/1182.md, germany/bund/acts/grundgesetz/artikel/016a.md or united-kingdom/uk/legislation/uksi/2014/1530/regulation/13.md. Use find_provision to look one up."New value: +"A provision file, for example united-states/federal/usc/title-11/1182.md, from find_provision."

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, closed-world), and the description goes beyond them by explaining that results come in groups, that a definition's own scope ("In this subchapter") is included, and why the answer matters ("a change to this provision can change what they mean"). It does not mention pagination behavior, though offset/max_results in the schema imply it.

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?

Purpose is front-loaded in the first clause, and the second sentence handles timing and rationale. The first sentence is dense—two nested parentheticals plus a quoted example—but each element is informative rather than filler.

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?

For a four-parameter, read-only lookup with a full-coverage schema, existing annotations, and an output schema, the description supplies what remains: the two result groupings, the definition-scope field, and the dependency rationale. Nothing needed to call or interpret 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 coverage is 100%, so date, path, offset, and max_results are already documented. The description reinforces the temporal semantics (the dependency set is evaluated "on a date") but adds no format, edge-case, or relationship details beyond the schema's own wording.

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?

Opens with a precise verb-and-resource framing: which provisions cite or use the definitions of this one, as of a date. It decomposes the result into two named groups (citers and term-users) with a concrete example ("debtor in possession"), so an agent can distinguish it from read_law, provision_history, or a plain text search without opening the 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?

Explicitly prescribes timing: "Use it before a text search when asked what depends on a provision or its definitions," which gives a clear selection rule against search_law. It offers no explicit when-not or negative case beyond that, so it falls short of a full routing rule set.

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.