Private Law Wiki

List reviewed native topics

answer_objects

Read-onlyIdempotent

List topics with at least one currently available whole answer cell. Each object carries answerCount: distinct available questions in the requested locale, not variants, sources or articles. Limit is an upper bound: counted pages emit at most 4 objects and at most 64 candidate pairs. Follow nextCursor until null; total counts matching objects, not answers. Counts are observed in one read-only snapshot per page at countObservedAt; pages are not one shared snapshot. Invalid cursors or incomplete counts return an error, never partial or stale numbers. Availability does not establish current law or personal applicability.

Input Schema

Name	Required	Description
`type`	No	Filter by object type, e.g. state, program, regime, bank, legal_form.
`limit`	No	Requested upper bound; default 100, maximum 250. Counted pages return at most 4 objects and may be shorter to respect the 64 candidate-pair budget; follow nextCursor.
`cursor`	No	Opaque pagination cursor: the exact nextCursor returned by the previous call. Omit for the first page.
`locale`	No	Answer language; Russian when omitted.

Output Schema

Name	Required	Description
`error`	No
`total`	No	Every object matching the type filter, across all pages.
`reason`	No
`objects`	No
`revision`	No
`nextCursor`	No	Pass as cursor for the next page; null on the last page.
`countObservedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 25, 2026

changedInput schema / properties / limit / description

Previous value: -"Page size; default 100 (sized to fit common client response limits), maximum 250."New value: +"Requested upper bound; default 100, maximum 250. Counted pages return at most 4 objects and may be shorter to respect the 64 candidate-pair budget; follow nextCursor."

addedOutput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "objects",
+      "total",
+      "nextCursor",
+      "revision",
+      "countObservedAt"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / countObservedAt
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / objects / items / properties / answerCount

Added value: +{
+  "description": "Distinct currently available whole question cells in this locale.",
+  "minimum": 1,
+  "type": "integer"
+}

changedOutput schema / properties / objects / items / required

Previous value: -[
-  "code",
-  "name",
-  "type",
-  "url",
-  "provenance"
-]New value: +[
+  "code",
+  "name",
+  "type",
+  "url",
+  "provenance",
+  "answerCount"
+]

addedOutput schema / properties / reason
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / required

Removed value: -[
-  "objects",
-  "total",
-  "nextCursor",
-  "revision"
-]

Changed5 schema fields changedOct 20, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Opaque pagination cursor: the exact nextCursor returned by the previous call. Omit for the first page.",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Page size; default 100 (sized to fit common client response limits), maximum 250.",
+  "maximum": 250,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / nextCursor

Added value: +{
+  "description": "Pass as cursor for the next page; null on the last page.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / total

Added value: +{
+  "description": "Every object matching the type filter, across all pages.",
+  "type": "integer"
+}

changedOutput schema / required

Previous value: -[
-  "objects",
-  "revision"
-]New value: +[
+  "objects",
+  "total",
+  "nextCursor",
+  "revision"
+]

Changed2 schema fields changedOct 17, 2026

removedOutput schema / properties / objects / items / properties / questions
```
Removed value: -{
-  "type": "integer"
-}
```

changedOutput schema / properties / objects / items / required

Previous value: -[
-  "code",
-  "name",
-  "type",
-  "questions",
-  "url",
-  "provenance"
-]New value: +[
+  "code",
+  "name",
+  "type",
+  "url",
+  "provenance"
+]

AddedOct 15, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses important behavioral traits: counted pages may emit only 4 objects due to a 64 candidate-pair budget, counts are per-page snapshots at countObservedAt rather than one shared snapshot, and invalid cursors or incomplete counts return an error rather than partial or stale numbers. It also carries an availability disclaimer excluding legal applicability.

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 dense but front-loaded around the core inclusion condition and answerCount semantics. Most sentences earn their place by clarifying counting, pagination, snapshot behavior, and error semantics, though the legal-availability disclaimer is somewhat boilerplate.

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 an output schema exists, the description does not need to explain return shape, and it still adds useful return-related semantics such as answerCount and total meaning. It is largely complete for a read-only list tool, with only the domain term 'whole answer cell' left somewhat opaque.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning about limit as an upper bound interacting with counted-page budgets and instructs following nextCursor until null. It also clarifies that answerCount reflects distinct available questions in the requested locale, not variants, sources, or articles.

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 ('List topics') plus a precise inclusion condition ('with at least one currently available whole answer cell'). It does not explicitly distinguish itself from siblings such as answer_lookup or search, but its enumeration-oriented purpose is otherwise clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives pagination mechanics but no explicit guidance on when to use this tool instead of answer_lookup, answer_compare, ask, or search. An agent must infer that this is the enumeration path rather than a targeted lookup path.

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?