Probative legal-marketing data

Compare keys in a dataset

data_compare

Read-onlyIdempotent

Compare up to 10 states, counties or other keys of one dataset side by side, e.g. lawyer pay or bar pass rates in two states. Results are not legal advice.

Input Schema

Name	Required	Default
`keys`	Yes
`dataset`	Yes
`response_format`	No	concise

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / dataset / enum

Previous value: -[
-  "bankruptcy",
-  "bar-pipeline",
-  "benchmarks",
-  "ca-courts",
-  "civil-filings",
-  "consumer-complaints",
-  "consumer-sentinel",
-  "criminal-filings",
-  "crosswalks",
-  "deserts",
-  "disability-hearings",
-  "eeoc-charges",
-  "fatal-crashes",
-  "fees",
-  "filing",
-  "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: +[
+  "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"
+]

Changed2 schema fields changedOct 28, 2026

removedInput schema / properties / detail

Removed value: -{
-  "default": "summary",
-  "enum": [
-    "summary",
-    "full"
-  ],
-  "type": "string"
-}

addedInput schema / properties / response_format

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

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / dataset / enum

Previous value: -[
-  "bankruptcy",
-  "bar-pipeline",
-  "benchmarks",
-  "ca-courts",
-  "civil-filings",
-  "consumer-complaints",
-  "consumer-sentinel",
-  "crosswalks",
-  "deserts",
-  "disability-hearings",
-  "eeoc-charges",
-  "fatal-crashes",
-  "fees",
-  "filing",
-  "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",
-  "veterans-representation",
-  "work-injuries"
-]New value: +[
+  "bankruptcy",
+  "bar-pipeline",
+  "benchmarks",
+  "ca-courts",
+  "civil-filings",
+  "consumer-complaints",
+  "consumer-sentinel",
+  "criminal-filings",
+  "crosswalks",
+  "deserts",
+  "disability-hearings",
+  "eeoc-charges",
+  "fatal-crashes",
+  "fees",
+  "filing",
+  "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 28, 2026

removedInput schema / properties / dataset / description

Removed value: -"Dataset id (list_datasets describes each one)"

changedInput schema / properties / dataset / enum

Previous value: -[
-  "bankruptcy",
-  "bar-pipeline",
-  "benchmarks",
-  "ca-courts",
-  "civil-filings",
-  "consumer-complaints",
-  "consumer-sentinel",
-  "crosswalks",
-  "deserts",
-  "disability-hearings",
-  "eeoc-charges",
-  "fatal-crashes",
-  "fees",
-  "filing",
-  "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",
-  "veterans-representation",
-  "work-injuries"
-]New value: +[
+  "bankruptcy",
+  "bar-pipeline",
+  "benchmarks",
+  "ca-courts",
+  "civil-filings",
+  "consumer-complaints",
+  "consumer-sentinel",
+  "crosswalks",
+  "deserts",
+  "disability-hearings",
+  "eeoc-charges",
+  "fatal-crashes",
+  "fees",
+  "filing",
+  "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",
+  "veterans-representation",
+  "work-injuries"
+]

removedInput schema / properties / detail / description

Removed value: -"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."

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 / dataset / enum

Previous value: -[
-  "bankruptcy",
-  "bar-pipeline",
-  "benchmarks",
-  "ca-courts",
-  "civil-filings",
-  "consumer-complaints",
-  "deserts",
-  "eeoc-charges",
-  "fatal-crashes",
-  "fees",
-  "filing",
-  "idb-civil",
-  "immigration-courts",
-  "language",
-  "law-firm-economy",
-  "law-offices",
-  "lawyer-wages",
-  "legal-prices",
-  "limitations",
-  "mdl",
-  "opinions",
-  "platforms",
-  "referral",
-  "robocall-complaints",
-  "state-courts",
-  "veterans-representation",
-  "work-injuries"
-]New value: +[
+  "bankruptcy",
+  "bar-pipeline",
+  "benchmarks",
+  "ca-courts",
+  "civil-filings",
+  "consumer-complaints",
+  "consumer-sentinel",
+  "crosswalks",
+  "deserts",
+  "disability-hearings",
+  "eeoc-charges",
+  "fatal-crashes",
+  "fees",
+  "filing",
+  "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",
+  "veterans-representation",
+  "work-injuries"
+]

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / dataset / enum

Previous value: -[
-  "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: +[
+  "bankruptcy",
+  "bar-pipeline",
+  "benchmarks",
+  "ca-courts",
+  "civil-filings",
+  "consumer-complaints",
+  "deserts",
+  "eeoc-charges",
+  "fatal-crashes",
+  "fees",
+  "filing",
+  "idb-civil",
+  "immigration-courts",
+  "language",
+  "law-firm-economy",
+  "law-offices",
+  "lawyer-wages",
+  "legal-prices",
+  "limitations",
+  "mdl",
+  "opinions",
+  "platforms",
+  "referral",
+  "robocall-complaints",
+  "state-courts",
+  "veterans-representation",
+  "work-injuries"
+]

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / dataset / enum

Previous value: -[
-  "benchmarks",
-  "ca-courts",
-  "fees",
-  "filing",
-  "language",
-  "mdl",
-  "opinions",
-  "platforms",
-  "referral"
-]New value: +[
+  "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"
+]

Changed2 schema fields changedOct 28, 2026

changedInput schema / properties / dataset / enum

Previous value: -[
-  "ca-courts",
-  "fees",
-  "filing",
-  "language",
-  "mdl",
-  "opinions",
-  "platforms"
-]New value: +[
+  "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"
+}

AddedOct 27, 2026

TDQS

B3.4/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 behavior, so the safety profile is covered. The description adds only the 10-key ceiling and a 'not legal advice' disclaimer; it does not explain what 'concise' vs 'detailed' output changes or whether keys must belong to the same dataset dimension.

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 short sentences: the capability and its scope come first, then a caveat. No filler, though the disclaimer occupies a slot that could have documented response_format or dataset semantics.

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?

An output schema exists, so return values needn't be described. Still, with two enums and a 37-value dataset list at 0% schema coverage, the description leaves meaningful gaps: whether keys can be mixed across datasets, what response_format does, and how results are shaped by dataset choice.

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 description coverage is 0%, so the description has to carry the load. It usefully clarifies that 'keys' means states, counties, or similar identifiers (the schema only says strings), but leaves the large dataset enum and the response_format parameter entirely unexplained.

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 verb and resource (compare keys of one dataset side by side) and gives concrete examples of keys. It doesn't distinguish itself from the sibling compare_states or data_lookup, so an agent can't tell from the description alone which comparison tool to pick, but the core purpose is unambiguous.

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?

Implies usage through the example ('lawyer pay or bar pass rates in two states') and the 'up to 10 keys' ceiling, which hints at lightweight side-by-side comparison. There is no explicit when-to-use versus compare_states, data_lookup, or data_search, and no exclusions.

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?