Probative legal-marketing data

How to cite

cite

Read-onlyIdempotent

The citation sentence, credit line, DOI and URL to cite: for a whole dataset, for one state, or for one rule cell (dataset "rules" with state and topic), or for one record id in another dataset. CC BY 4.0 asks for credit and a link.

Input Schema

Name	Required	Description	Default
`id`	No	Other datasets: the record id
`state`	No	rules only: two-letter code, or DC
`topic`	No	rules only: topic key, e.g. filing
`detail`	No	summary (default): each record as its id, a 1-2 sentence text, status, date checked, one source URL and the page to cite. full: every field, every source and the per-record provenance.	summary
`dataset`	No	Dataset id (list_datasets shows them)	rules

Output Schema

Name	Required	Description
`meta`	Yes	Credit line (attribution), citation, DOI, version, license (CC BY 4.0), disclaimer, notice and the page to cite
`nextCursor`	No	Pass as `cursor` to get the next page; null on the last page
`provenance`	Yes	Where this came from: the publisher of the dataset, the dataset and its version DOI, the record id, the original source (who published it and its URL), the day that source was last checked, and when this answer was retrieved

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

changedInput schema / properties / dataset / enum

Previous value: -[
-  "rules",
-  "ca-courts",
-  "fees",
-  "filing",
-  "language",
-  "mdl",
-  "opinions",
-  "platforms"
-]New value: +[
+  "rules",
+  "benchmarks",
+  "ca-courts",
+  "fees",
+  "filing",
+  "language",
+  "mdl",
+  "opinions",
+  "platforms",
+  "referral"
+]

addedInput schema / properties / detail

Added value: +{
+  "default": "summary",
+  "description": "summary (default): each record as its id, a 1-2 sentence text, status, date checked, one source URL and the page to cite. full: every field, every source and the per-record provenance.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}

Changed6 schema fields changedOct 27, 2026

addedInput schema / properties / id / maxLength
```
Added value: +120
```
addedInput schema / properties / state / maxLength
```
Added value: +40
```
addedInput schema / properties / topic / maxLength
```
Added value: +40
```

addedOutput schema / properties / nextCursor

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

addedOutput schema / properties / provenance

Added value: +{
+  "description": "Where this came from: the publisher of the dataset, the dataset and its version DOI, the record id, the original source (who published it and its URL), the day that source was last checked, and when this answer was retrieved",
+  "properties": {
+    "citeUrl": {
+      "description": "The page to cite",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dataset": {
+      "description": "Dataset id",
+      "type": "string"
+    },
+    "datasetTitle": {
+      "type": "string"
+    },
+    "dateChecked": {
+      "description": "YYYY-MM-DD the record was last checked against its source",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "doi": {
+      "description": "Version DOI",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "doiUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "line": {
+      "description": "The same facts as one sentence, to quote under an answer",
+      "type": "string"
+    },
+    "publisher": {
+      "description": "Publisher of the dataset",
+      "type": "string"
+    },
+    "recordId": {
+      "description": "Stable id of the record",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "retrievedAt": {
+      "description": "ISO 8601 time this answer was served",
+      "type": "string"
+    },
+    "source": {
+      "description": "The original source: statute, rule, bar opinion, court report, agency table or platform policy",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sourceKind": {
+      "description": "primary or secondary",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sourceUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "P primary source, S secondary, D default (no specific rule found), U open question",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "version": {
+      "description": "Dataset version",
+      "type": "string"
+    }
+  },
+  "required": [
+    "publisher",
+    "dataset",
+    "version",
+    "retrievedAt"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "meta"
-]New value: +[
+  "meta",
+  "provenance"
+]

First observedOct 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish that this is read-only, idempotent, non-destructive, and closed-world, so the description need not restate safety. The description adds useful behavioral context by disclosing the citation components returned and the CC BY attribution/link expectation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loads what the tool returns, and then explains scope and licensing context. It is dense but appropriately sized for a citation tool.

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?

Given the full schema, rich annotations, and presence of an output schema, the description covers the remaining agent-relevant context: what citation elements are produced and which scope combinations are supported. Nothing essential is missing for correct invocation.

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 the schema already documents each parameter. The description still adds value by clarifying how dataset, state, topic, and id map to citation scopes: whole dataset, one state, one rule cell, or one record in another dataset.

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 clearly states the resource and output: citation sentence, credit line, DOI, and URL, with scope variants for whole dataset, state, rule cell, or record id. It does not explicitly contrast itself with sibling lookup/search tools, so it is clear but not fully differentiated.

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 gives clear usage context by explaining that the tool is for citing a whole dataset, a state, a rule cell, or another dataset record, and ties this to CC BY 4.0 attribution needs. It does not name alternatives or explicitly state when not to use it.

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

All Probative legal-marketing data 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?