Skip to main content
Glama

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

Lawyer advertising rules for one state

get_state_rules
Read-onlyIdempotent

Every lawyer advertising rule for one US state or DC in one call: filing, disclaimers, waiting periods, claims, referrals, language, recording, texting, privacy. Results are not legal advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "get_state_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter code (TX), or DC. Full names (Texas) also work.
topicNo
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / topic
      Added value: +{
      +  "enum": [
      +    "intake-vendor"
      +  ],
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • 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"
      -  }
      -}
  3. Changed1 schema field 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"
      +}
  4. Changed3 schema fields changed
    • 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"
      +]
  5. First observed

TDQS

A3.6/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 covered. The description adds only the 'not legal advice' caveat and an implicit completeness promise; it says nothing about how current the rules are, whether they are updated over time, or any rate/usage limits.

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?

The scope is front-loaded in a single dense sentence followed by a short disclaimer, with no filler. The topic enumeration is long but each term functions as a coverage cue, though it reads as a list rather than organized structure.

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

Completeness4/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 need no explanation, and annotations carry the safety profile. What remains missing is any guidance on the undocumented 'topic' parameter and on routing versus sibling tools, which is a moderate rather than severe gap for a read-only lookup.

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 33%: the 'state' parameter is well documented in the schema, and 'response_format' is self-evident from its enum and default. The 'topic' enum value 'intake-vendor' is completely opaque and the description never mentions 'topic' at all, so the gap is not compensated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb-plus-resource ('Every lawyer advertising rule for one US state or DC') and enumerates the covered domains (filing, disclaimers, waiting periods, claims, referrals, language, recording, texting, privacy). That coverage list lets an agent distinguish this comprehensive per-state lookup from narrower siblings like get_rule or search_rules without opening any schema.

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 phrase 'in one call' implies this is the bulk/complete retrieval option, which hints at when to prefer it, but the description never states when not to use it and names no alternative tool. The agent must infer routing from sibling names alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources