Probative legal-marketing data

This connector has been deprecated

Duplicate listing. The maintained listing for this server is Probative legal-marketing data, synced with the official MCP Registry entry com.probativegrowth/legal-marketing-data. Same endpoint: https://probativegrowth.com/mcp

What changed

whats_new

Read-onlyIdempotent

What changed lately in any of the datasets (or only the datasets named), newest first, with the date and source of each. Optional since (YYYY-MM-DD).

Input Schema

Name	Required	Description	Default
`limit`	No
`since`	No
`state`	No
`datasets`	No	Dataset ids, e.g. rules, ad-costs, attorneys, aviation-accidents, bankruptcy. list_datasets lists every id.
`practice`	No
`response_format`	No		concise

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / datasets / description

Previous value: -"Dataset ids, e.g. rules, attorneys, aviation-accidents, bankruptcy, bar-pipeline. list_datasets lists every id."New value: +"Dataset ids, e.g. rules, ad-costs, attorneys, aviation-accidents, bankruptcy. list_datasets lists every id."

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / datasets / description

Previous value: -"Dataset ids, e.g. rules, attorneys, bankruptcy, bar-pipeline, benchmarks. list_datasets lists every id."New value: +"Dataset ids, e.g. rules, attorneys, aviation-accidents, bankruptcy, bar-pipeline. list_datasets lists every id."

Changed3 schema fields changedOct 29, 2026

changedInput schema / properties / datasets / description

Previous value: -"Dataset ids, e.g. rules, bankruptcy, bar-pipeline, benchmarks, business-applications. list_datasets lists every id."New value: +"Dataset ids, e.g. rules, attorneys, bankruptcy, bar-pipeline, benchmarks. list_datasets lists every id."

addedInput schema / properties / practice

Added value: +{
+  "maxLength": 80,
+  "type": "string"
+}

addedInput schema / properties / state

Added value: +{
+  "maxLength": 40,
+  "type": "string"
+}

Changed2 schema fields changedOct 29, 2026

addedInput schema / properties / datasets / description

Added value: +"Dataset ids, e.g. rules, bankruptcy, bar-pipeline, benchmarks, business-applications. list_datasets lists every id."

removedInput schema / properties / datasets / items / enum

Removed value: -[
-  "rules",
-  "bankruptcy",
-  "bar-pipeline",
-  "benchmarks",
-  "ca-courts",
-  "civil-filings",
-  "consumer-complaints",
-  "consumer-sentinel",
-  "criminal-filings",
-  "crosswalks",
-  "deserts",
-  "disability-hearings",
-  "eeoc-charges",
-  "fatal-crashes",
-  "federal-filings-county",
-  "fees",
-  "filing",
-  "findings",
-  "firm-web-census",
-  "idb-civil",
-  "immigration-courts",
-  "language",
-  "law-firm-economy",
-  "law-offices",
-  "lawyer-wages",
-  "legal-need",
-  "legal-prices",
-  "limitations",
-  "mdl",
-  "nursing-homes",
-  "opinions",
-  "platforms",
-  "referral",
-  "robocall-complaints",
-  "state-courts",
-  "truck-crashes",
-  "va-compensation",
-  "vehicle-complaints",
-  "veterans-representation",
-  "wage-enforcement",
-  "work-injuries"
-]

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / datasets / items / enum

Previous value: -[
-  "rules",
-  "bankruptcy",
-  "bar-pipeline",
-  "benchmarks",
-  "ca-courts",
-  "civil-filings",
-  "consumer-complaints",
-  "consumer-sentinel",
-  "criminal-filings",
-  "crosswalks",
-  "deserts",
-  "disability-hearings",
-  "eeoc-charges",
-  "fatal-crashes",
-  "fees",
-  "filing",
-  "findings",
-  "idb-civil",
-  "immigration-courts",
-  "language",
-  "law-firm-economy",
-  "law-offices",
-  "lawyer-wages",
-  "legal-need",
-  "legal-prices",
-  "limitations",
-  "mdl",
-  "nursing-homes",
-  "opinions",
-  "platforms",
-  "referral",
-  "robocall-complaints",
-  "state-courts",
-  "truck-crashes",
-  "va-compensation",
-  "vehicle-complaints",
-  "veterans-representation",
-  "wage-enforcement",
-  "work-injuries"
-]New value: +[
+  "rules",
+  "bankruptcy",
+  "bar-pipeline",
+  "benchmarks",
+  "ca-courts",
+  "civil-filings",
+  "consumer-complaints",
+  "consumer-sentinel",
+  "criminal-filings",
+  "crosswalks",
+  "deserts",
+  "disability-hearings",
+  "eeoc-charges",
+  "fatal-crashes",
+  "federal-filings-county",
+  "fees",
+  "filing",
+  "findings",
+  "firm-web-census",
+  "idb-civil",
+  "immigration-courts",
+  "language",
+  "law-firm-economy",
+  "law-offices",
+  "lawyer-wages",
+  "legal-need",
+  "legal-prices",
+  "limitations",
+  "mdl",
+  "nursing-homes",
+  "opinions",
+  "platforms",
+  "referral",
+  "robocall-complaints",
+  "state-courts",
+  "truck-crashes",
+  "va-compensation",
+  "vehicle-complaints",
+  "veterans-representation",
+  "wage-enforcement",
+  "work-injuries"
+]

Changed4 schema fields changedOct 29, 2026

changedInput schema / properties / datasets / items / enum

Previous value: -[
-  "rules",
-  "bar-pipeline",
-  "benchmarks",
-  "ca-courts",
-  "civil-filings",
-  "consumer-complaints",
-  "deserts",
-  "eeoc-charges",
-  "fatal-crashes",
-  "fees",
-  "filing",
-  "language",
-  "law-offices",
-  "lawyer-wages",
-  "legal-prices",
-  "limitations",
-  "mdl",
-  "opinions",
-  "platforms",
-  "referral",
-  "robocall-complaints",
-  "state-courts"
-]New value: +[
+  "rules",
+  "bankruptcy",
+  "bar-pipeline",
+  "benchmarks",
+  "ca-courts",
+  "civil-filings",
+  "consumer-complaints",
+  "consumer-sentinel",
+  "criminal-filings",
+  "crosswalks",
+  "deserts",
+  "disability-hearings",
+  "eeoc-charges",
+  "fatal-crashes",
+  "fees",
+  "filing",
+  "findings",
+  "idb-civil",
+  "immigration-courts",
+  "language",
+  "law-firm-economy",
+  "law-offices",
+  "lawyer-wages",
+  "legal-need",
+  "legal-prices",
+  "limitations",
+  "mdl",
+  "nursing-homes",
+  "opinions",
+  "platforms",
+  "referral",
+  "robocall-complaints",
+  "state-courts",
+  "truck-crashes",
+  "va-compensation",
+  "vehicle-complaints",
+  "veterans-representation",
+  "wage-enforcement",
+  "work-injuries"
+]

removedInput schema / properties / detail

Removed 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"
-}

addedInput schema / properties / response_format

Added value: +{
+  "default": "concise",
+  "enum": [
+    "concise",
+    "detailed"
+  ],
+  "type": "string"
+}

removedOutput schema / properties

Removed value: -{
-  "meta": {
-    "description": "Credit line (attribution), citation, DOI, version, license (CC BY 4.0), disclaimer, notice and the page to cite",
-    "required": [
-      "attribution",
-      "license",
-      "disclaimer",
-      "notice"
-    ],
-    "type": "object"
-  },
-  "nextCursor": {
-    "description": "Pass as `cursor` to get the next page; null on the last page",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "provenance": {
-    "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"
-  }
-}

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / datasets / items / enum

Previous value: -[
-  "rules",
-  "bar-pipeline",
-  "benchmarks",
-  "ca-courts",
-  "civil-filings",
-  "deserts",
-  "eeoc-charges",
-  "fees",
-  "filing",
-  "language",
-  "law-offices",
-  "limitations",
-  "mdl",
-  "opinions",
-  "platforms",
-  "referral",
-  "robocall-complaints",
-  "state-courts"
-]New value: +[
+  "rules",
+  "bar-pipeline",
+  "benchmarks",
+  "ca-courts",
+  "civil-filings",
+  "consumer-complaints",
+  "deserts",
+  "eeoc-charges",
+  "fatal-crashes",
+  "fees",
+  "filing",
+  "language",
+  "law-offices",
+  "lawyer-wages",
+  "legal-prices",
+  "limitations",
+  "mdl",
+  "opinions",
+  "platforms",
+  "referral",
+  "robocall-complaints",
+  "state-courts"
+]

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / datasets / items / enum

Previous value: -[
-  "rules",
-  "bar-pipeline",
-  "benchmarks",
-  "ca-courts",
-  "civil-filings",
-  "deserts",
-  "fees",
-  "filing",
-  "language",
-  "law-offices",
-  "limitations",
-  "mdl",
-  "opinions",
-  "platforms",
-  "referral",
-  "state-courts"
-]New value: +[
+  "rules",
+  "bar-pipeline",
+  "benchmarks",
+  "ca-courts",
+  "civil-filings",
+  "deserts",
+  "eeoc-charges",
+  "fees",
+  "filing",
+  "language",
+  "law-offices",
+  "limitations",
+  "mdl",
+  "opinions",
+  "platforms",
+  "referral",
+  "robocall-complaints",
+  "state-courts"
+]

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / datasets / items / enum

Previous value: -[
-  "rules",
-  "benchmarks",
-  "ca-courts",
-  "fees",
-  "filing",
-  "language",
-  "mdl",
-  "opinions",
-  "platforms",
-  "referral"
-]New value: +[
+  "rules",
+  "bar-pipeline",
+  "benchmarks",
+  "ca-courts",
+  "civil-filings",
+  "deserts",
+  "fees",
+  "filing",
+  "language",
+  "law-offices",
+  "limitations",
+  "mdl",
+  "opinions",
+  "platforms",
+  "referral",
+  "state-courts"
+]

Changed3 schema fields changedOct 28, 2026

changedInput schema / properties / datasets / items / 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"
+}

changedInput schema / properties / limit / default
```
Previous value: -25New value: +5
```

Changed3 schema fields changedOct 27, 2026

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

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: results are ordered newest-first and each entry carries a date and source. It says nothing about the effect of `limit`, the default of 5, or how `response_format` changes output.

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?

A single front-loaded sentence that packs scope, ordering, returned fields, and the `since` format with no filler. It is efficient, though the extreme terseness defers needed explanation of the remaining filters.

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

Completeness2/5

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

With six parameters, 17% schema coverage, and no sibling differentiation, the description leaves too much unsaid. An output schema exists so return values needn't be spelled out, but the meaning of `state` and `practice` and the tradeoff between `concise` and `detailed` are absent everywhere.

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

Parameters2/5

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

Schema description coverage is only 17% — just `datasets` is documented — so the description carries most of the burden. It clarifies `since` as optional YYYY-MM-DD, but `limit`, `state`, `practice`, and `response_format` are left entirely unexplained in both places; an agent cannot tell whether `state` filters datasets or changes.

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?

States a specific resource and scope: recent changes across any dataset or a named subset, returned newest-first with date and source. An agent can grasp the tool's role immediately, but the description never distinguishes it from the sibling `list_rule_changes`, which plausibly overlaps.

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?

The parenthetical 'or only the `datasets` named' implies a filtering mode, but there is no explicit statement of when to reach for this versus `list_rule_changes` or `list_datasets`, nor any prerequisite context. Usage is inferable from the changelog framing rather than stated.

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?