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

Law-firm marketing benchmarks

get_benchmark

Read-onlyIdempotent

Law-firm marketing benchmarks (ad costs, call outcomes, speed to sign), as bands, tiers and rounded values with the methods page to cite.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_benchmark"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No	Optional words to keep only matching rows, e.g. "hour" or…
`table`	No
`v5_table`	No
`public_table`	No
`response_format`	No		concise

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026

addedInput schema / properties / public_table

Added value: +{
+  "enum": [
+    "serp-landscape",
+    "law-firm-websites",
+    "demand-per-law-office",
+    "legal-profession-figures"
+  ],
+  "type": "string"
+}

addedInput schema / properties / v5_table

Added value: +{
+  "enum": [
+    "other-google-ad-types",
+    "injury-search-clicks-and-season",
+    "injury-google-ads-spend-mix",
+    "lsa-lead-timing-and-charges",
+    "lsa-call-lengths"
+  ],
+  "type": "string"
+}

Changed5 schema fields changedOct 29, 2026

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

changedInput schema / properties / query / description

Previous value: -"Optional words to keep only matching rows, e.g. \"hour\" or \"Local Services\""New value: +"Optional words to keep only matching rows, e.g. \"hour\" or…"

addedInput schema / properties / response_format

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

removedInput schema / properties / table / description

Removed value: -"The table id (the benchmarks dataset key). Leave out to list the tables."

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

Previous value: -[
-  "speed-to-sign",
-  "calls-and-hours",
-  "organic-ai"
-]New value: +[
+  "speed-to-sign",
+  "calls-and-hours",
+  "organic-ai",
+  "search-click-costs",
+  "search-query-patterns",
+  "ad-call-outcomes",
+  "lsa-lead-mix",
+  "quarterly-demand",
+  "cost-per-signed-client"
+]

AddedOct 28, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: values are bands, tiers and rounded numbers rather than exact figures, and a methods page exists to cite. It says nothing about pagination, result size, or what happens when query matches nothing.

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 dense sentence with no filler, front-loaded with the resource name and immediately followed by the covered topics. It is efficient, though the trailing clause about bands/rounding and the methods page is slightly compressed into the same breath as the content list.

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?

An output schema exists, so return shape needs no explanation, but with five inputs and three separate table-selection enums the description leaves the agent without a rule for picking a table or interpreting concise vs detailed. For a multi-domain benchmark lookup, the description stops short of what is needed to call it confidently.

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 20%, and only the query parameter carries a description. The description does not explain the relationship between the three mutually exclusive-looking table selectors (table, v5_table, public_table) or how a caller should choose among them, which is the single most consequential decision for invoking this tool correctly. It also never mentions response_format.

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?

Names the resource precisely (law-firm marketing benchmarks) and enumerates the content domains it covers — ad costs, call outcomes, speed to sign — so an agent knows what class of data comes back. It implicitly separates itself from rule/filing/citation siblings, though it never names a sibling explicitly.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative among the many data_* and search tools. The only usage signal is an implicit one: figures come as bands/tiers/rounded values and should be cited to a methods page, which hints at presentation but not at tool selection.

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?