Global law

Phrase history

phrase_history

Read-onlyIdempotent

When words came into the law and when they left it, at any date and in every jurisdiction: each change whose added or removed text contains them. Use it for things no longer in force (for example "COVID" in the Grundgesetz).

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": {
      "query": "<query>"
    },
    "name": "phrase_history"
  }
}

Input Schema

Name	Required	Description
`kind`	No	laws (default; "law" is read the same): law only. judgments: court decisions (case law) only. all: both. A jurisdiction that names case law (a path ending in /caselaw) reads it too.
`query`	Yes	Words or a phrase to trace, as plain text (either case, and dashes and quotes in any of their forms, match); a regular expression if regex is true.
`regex`	No	Read query as a regular expression (POSIX extended, as git grep -E reads it) instead of plain text (default false).
`offset`	No	Rows to skip: the next_offset the answer before gave in "page" (default 0).
`max_results`	No	At most this many (default 40, at most 300).
`jurisdiction`	No	Optional jurisdiction prefix, for example "germany", "united-states/federal" or "united-kingdom/uk/legislation/uksi".

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 10, 2026

changedInput schema / properties / kind / description

Previous value: -"law (default): bodies of law only. judgments: court decisions (case law) only. Case law is also read when the jurisdiction names it (a path ending in /caselaw)."New value: +"laws (default; \"law\" is read the same): law only. judgments: court decisions (case law) only. all: both. A jurisdiction that names case law (a path ending in /caselaw) reads it too."

changedInput schema / properties / kind / enum

Previous value: -[
-  "law",
-  "judgments"
-]New value: +[
+  "laws",
+  "judgments",
+  "all",
+  "law"
+]

changedInput schema / properties / max_results / description

Previous value: -"At most this many (default 40)."New value: +"At most this many (default 40, at most 300)."

addedInput schema / properties / offset

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

addedInput schema / properties / query / description

Added value: +"Words or a phrase to trace, as plain text (either case, and dashes and quotes in any of their forms, match); a regular expression if regex is true."

addedInput schema / properties / regex / description

Added value: +"Read query as a regular expression (POSIX extended, as git grep -E reads it) instead of plain text (default false)."

First observedNov 10, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add scope. It does add one useful behavioral fact — results are changes whose added or removed text matches — but says nothing about ordering, whether a term's full lifespan is returned in one pass, or how broad 'every jurisdiction' search behaves.

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 tight sentences with no filler, and the core purpose is front-loaded before the usage example. The opening clause is a little ornate for a tool description but costs only one clause.

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

Completeness3/5

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

With a full output schema and rich annotations, the definition only needs to frame scope and intent. It mostly does, but the undefined 'date' language and the absence of any note on what a 'change' represents leave a small conceptual gap for a diff-oriented tool.

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 kinds, regex, paging and limits are already documented; baseline 3 applies. The description adds no parameter-level meaning beyond that. It also says 'at any date', yet the schema exposes no date parameter, which could mislead an agent looking for one.

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 names a specific resource (every change whose added or removed text contains the words) and a specific lens (when words entered/left the law). That is meaningfully distinct from siblings like search_law or search_changes. It is only slightly weakened by the poetic framing 'came into the law and when they left it', which takes a moment to decode as 'track term lifetime across amendments'.

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?

It gives one concrete when-to-use signal ('things no longer in force', with a COVID/Grundgesetz example), which is genuinely helpful. However, it never names an alternative or states when NOT to use it, so an agent comparing it against a provision-history or search_changes sibling still has to infer the boundary.

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.