Private Law Wiki

Search the Private Law wiki

search

Read-onlyIdempotent

Rank published articles for a query and return them with titles and URLs. Use when you want sources to read rather than a single answer. Search is sense-aware: bare MSO promotes only the Hong Kong Money Service Operator owner, professional-industry context promotes the regulated-practice platform, and genuinely conflicting context returns both with an explicit interpretation object.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Default 5.
`query`	Yes	Search terms or a question.
`locale`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hits`	Yes
`queryInterpretation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 11, 2026

changedOutput schema / properties / hits / items / properties / provenance / properties / version / description

Previous value: -"Revision of exactly the material served: article snapshot content hash (the HTML ETag value) or dataset version. Null when unknown."New value: +"Revision of exactly the material served: for an article the snapshot content hash (the HTML ETag value); for a dataset record the dataset revision it was published in, since the published file is named by the hash of its own content and meta.version plus datasets/index.json resolve that filename. Null when unknown."

Changed2 schema fields changedSep 10, 2026

addedOutput schema / properties / hits / items / properties / provenance

Added value: +{
+  "description": "Origin of one record: stable id, clean canonical URL, publisher, the exact published revision served, a ready citation, primary sources and review status.",
+  "properties": {
+    "canonical_url": {
+      "description": "Published location without tracking parameters.",
+      "format": "uri",
+      "type": "string"
+    },
+    "cite_as": {
+      "type": "string"
+    },
+    "contract": {
+      "const": "wiki-provenance/1",
+      "type": "string"
+    },
+    "id": {
+      "description": "<locale>:<slug> for an article, <dataset>:<record id> for a dataset row.",
+      "type": "string"
+    },
+    "primary_sources": {
+      "items": {
+        "properties": {
+          "name": {
+            "type": "string"
+          },
+          "url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "name",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "publisher": {
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "url": {
+          "format": "uri",
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "url"
+      ],
+      "type": "object"
+    },
+    "verification_status": {
+      "enum": [
+        "verified",
+        "pending",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "version": {
+      "description": "Revision of exactly the material served: article snapshot content hash (the HTML ETag value) or dataset version. Null when unknown.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "contract",
+    "id",
+    "canonical_url",
+    "publisher",
+    "version",
+    "cite_as",
+    "primary_sources",
+    "verification_status"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / hits / items / required

Previous value: -[
-  "slug",
-  "url"
-]New value: +[
+  "slug",
+  "url",
+  "provenance"
+]

Changed3 schema fields changedAug 17, 2026

changedOutput schema / properties / hits / items / properties / distance / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

addedOutput schema / properties / queryInterpretation

Added value: +{
+  "properties": {
+    "ambiguous": {
+      "type": "boolean"
+    },
+    "choices": {
+      "items": {
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "locale": {
+            "type": "string"
+          },
+          "sense": {
+            "enum": [
+              "hong_kong_money_service_operator",
+              "regulated_practice_management"
+            ],
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "sense",
+          "slug",
+          "locale",
+          "title",
+          "description",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "type": "string"
+    },
+    "sense": {
+      "enum": [
+        "hong_kong_money_service_operator",
+        "regulated_practice_management",
+        "comparison",
+        "ambiguous"
+      ],
+      "type": "string"
+    },
+    "term": {
+      "enum": [
+        "MSO"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "term",
+    "sense",
+    "ambiguous",
+    "message",
+    "choices"
+  ],
+  "type": [
+    "object",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "hits"
-]New value: +[
+  "hits",
+  "queryInterpretation"
+]

Changed5 schema fields changedAug 8, 2026

removedInput schema / properties / k

Removed value: -{
-  "default": 5,
-  "maximum": 10,
-  "minimum": 1,
-  "type": "integer"
-}

addedInput schema / properties / limit

Added value: +{
+  "description": "Default 5.",
+  "maximum": 20,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / locale

Added value: +{
+  "enum": [
+    "ru",
+    "en",
+    "ko",
+    "zh-hant"
+  ],
+  "type": "string"
+}

addedInput schema / properties / query / description
```
Added value: +"Search terms or a question."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "hits": {
+      "items": {
+        "properties": {
+          "distance": {
+            "type": "number"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "hits"
+  ],
+  "type": "object"
+}

First observedJul 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description rightly focuses on behavior beyond them: sense-aware disambiguation of 'MSO' and the fact that conflicting context yields both results plus an explicit interpretation object. This is genuinely useful context an agent cannot get from the annotations, though it does not cover result-count or locale-related behavior.

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?

Three sentences, front-loaded with purpose and usage before the denser disambiguation detail. The final sentence is long and example-heavy but each clause earns its place by clarifying real ambiguity resolution.

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?

With an output schema present, the description need not explain return values, and it covers purpose, usage, and the non-obvious disambiguation behavior. It omits any mention of locale handling or the default/maximum result count, which are minor gaps given the schema covers limit.

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 67%; query and limit are documented in the schema, but locale (an enum) has no description anywhere. The description illuminates how query context is interpreted (sense awareness) but says nothing about limit or locale, so it adds only partial meaning over the structured fields.

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?

States a specific verb and resource (ranks published articles in the Private Law wiki) and clearly distinguishes itself from the 'ask' sibling by offering sources to read rather than a single answer. An agent can route between the two tools 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 Guidelines5/5

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

Explicitly gives the selection condition: 'Use when you want sources to read rather than a single answer,' which names the alternative behavior (the 'ask' sibling) it is contrasted against. Nothing about when to pick this tool is left to inference.

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

All Private Law Wiki 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.

Resources

Need Help?