Skip to main content
Glama
Sign In

Probative legal-marketing data

by com.probativegrowth
OverviewDiscussionsAdmin
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

Bar ethics opinions on lawyer marketing

search_ethics_opinions
Read-onlyIdempotent

Bar ethics opinions (ABA and state) on lawyer marketing, e.g. pay-per-lead, Google reviews, AI chatbots, referral fees, social media. Results are not legal advice.

Input Schema

NameRequiredDescriptionDefault
limitNoRecords per page (1 to 25)
queryNoWords to match, e.g. "Google reviews" or "pay per lead"
stateNoTwo-letter code, DC, or ABA for the American Bar Association
topicNoOne of 27 values, e.g. advertising-general, fee-sharing, trade-names
cursorNoThe nextCursor from the previous page; leave out for the first…
in_force_onlyNoLeave out opinions marked withdrawn or superseded
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"The nextCursor from the previous page; leave out for the first page"New value: +"The nextCursor from the previous page; leave out for the first…"
    • 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"
+}
    • addedInput schema / properties / topic / description
      Added value: +"One of 27 values, e.g. advertising-general, fee-sharing, trade-names"
    • removedInput schema / properties / topic / enum
      Removed value: -[
-  "advertising-general",
-  "fee-sharing",
-  "trade-names",
-  "solicitation",
-  "lawyer-platforms",
-  "reviews",
-  "lead-generators",
-  "referral-services",
-  "websites",
-  "social-media",
-  "awards-ratings",
-  "testimonials",
-  "past-results",
-  "specialist-claims",
-  "office-address",
-  "competitor-keywords",
-  "pay-per-lead",
-  "client-intake",
-  "ai",
-  "ai-tools",
-  "domain-names",
-  "chatbots",
-  "client-lists-case-results",
-  "texting",
-  "spanish-or-other-language",
-  "waiting-period",
-  "call-recording"
-]
    • 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"
-  }
-}
  2. Changed1 schema field changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "advertising-general",
-  "fee-sharing",
-  "trade-names",
-  "solicitation",
-  "lawyer-platforms",
-  "reviews",
-  "lead-generators",
-  "referral-services",
-  "websites",
-  "social-media",
-  "awards-ratings",
-  "testimonials",
-  "past-results",
-  "specialist-claims",
-  "office-address",
-  "competitor-keywords",
-  "pay-per-lead",
-  "client-intake",
-  "ai-tools",
-  "domain-names",
-  "chatbots",
-  "client-lists-case-results",
-  "texting",
-  "spanish-or-other-language",
-  "waiting-period",
-  "call-recording"
-]New value: +[
+  "advertising-general",
+  "fee-sharing",
+  "trade-names",
+  "solicitation",
+  "lawyer-platforms",
+  "reviews",
+  "lead-generators",
+  "referral-services",
+  "websites",
+  "social-media",
+  "awards-ratings",
+  "testimonials",
+  "past-results",
+  "specialist-claims",
+  "office-address",
+  "competitor-keywords",
+  "pay-per-lead",
+  "client-intake",
+  "ai",
+  "ai-tools",
+  "domain-names",
+  "chatbots",
+  "client-lists-case-results",
+  "texting",
+  "spanish-or-other-language",
+  "waiting-period",
+  "call-recording"
+]
  3. Changed2 schema fields changed
    • 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: -10New value: +5
  4. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description adds little on that axis. It does contribute the domain boundary (ABA plus state bars) and the non-legal-advice caveat, but says nothing about result volume, ranking, or how pagination interacts with the cursor parameter.

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?

Two sentences, front-loaded with the resource and scope, with the disclaimer placed last where it belongs. Every clause carries information; there is no filler or restatement of the title.

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 and 86% of parameters are documented, so the description needn't explain returns. However, with seven parameters and zero required ones, the description never says what a call with no filters returns or which filters combine, which is a meaningful gap for a fully-optional search tool.

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 86%, so nearly every parameter is already documented in the schema, including query examples, the state/ABA convention, and cursor semantics. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the work.

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 names a specific resource (bar ethics opinions from ABA and state bars) and constrains it to lawyer marketing, with concrete example topics (pay-per-lead, Google reviews, AI chatbots, referral fees, social media). An agent can tell this apart from search_rules or get_rule by subject matter, though the verb itself is only implied by the tool name rather than stated.

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 statement of when to use this versus siblings such as search_rules, get_rule, or search, nor any exclusion criteria. The only guidance-like sentence, 'Results are not legal advice,' is a disclaimer rather than a usage rule, so the agent must infer routing from the name and topic examples alone.

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 toolsInspect
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