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

Law-firm market brief for one state

get_state_market_brief
Read-onlyIdempotent

Every public number about marketing a law firm in one state or DC, joined from nine open datasets. Each figure carries its source and check date. Not a forecast. 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_market_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter code (TX) or DC; full names (Texas) also work
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      -  }
      -}
  2. Added

TDQS

B3.3/5.0
Behavior4/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 real value beyond that: figures are joined from nine open datasets, each carries a source and check date, and the brief is explicitly not a forecast and not legal advice. What is missing is any note on coverage limits (e.g., whether all states are populated) or how concise versus detailed differ.

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?

Four short sentences, front-loaded with the scope statement before the caveats. Every sentence carries information and none is padded. The opening is a sentence fragment and the caveats read as boilerplate, but the length is well matched to the tool.

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 structure need not be explained, and the annotations carry the safety profile. The description still tells the agent what the payload conceptually contains (sourced, date-checked figures) and what it is not. The remaining gap is behavioral: no indication of which datasets back which figures or what happens for a state with thin data, which matters for a nine-source join.

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 coverage sits at 50%: the 'state' parameter is documented (two-letter code or full name), but 'response_format' has only an enum and default with no explanation of what the two modes actually return. The description adds nothing about either parameter, so it fails to compensate for the undocumented response_format. The agent must guess whether 'detailed' changes length, included datasets, or provenance rendering.

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 opening sentence states a specific resource and scope: all public marketing numbers for a single state or DC, aggregated from nine datasets. That is far more informative than the title alone and implicitly separates it from siblings like compare_states (multi-state) or get_state_rules (regulatory text). It stops short of naming any sibling explicitly, so the agent must infer the boundary.

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, when-not-to-use, or named alternative anywhere in the text. With 23 sibling tools including compare_states, get_state_rules, and get_benchmark, the agent gets no routing help for choosing this brief over those. The scope phrase 'marketing a law firm in one state' hints at a use case but never states one.

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