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

California court filings in one county

get_ca_court_filings
Read-onlyIdempotent

California only: cases filed in one county's superior court (or CA for the whole state) in fiscal year 2024-25, by case type, with the prior year. 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": {
      "county": "<county>"
    },
    "name": "get_ca_court_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNo
countyYesCounty name ("Los Angeles", "san-diego") or CA for the…
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / county / description
      Previous value: -"County name (\"Los Angeles\", \"san-diego\") or CA for the statewide row"New value: +"County name (\"Los Angeles\", \"san-diego\") or CA for the…"
    • 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"
      -}
    • removedInput schema / properties / group / description
      Removed value: -"Optional: one group of case types"
    • 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. 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"
      +}
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare the operation as read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful temporal scope (fiscal year 2024-25 with prior year) and a legal disclaimer, but it does not disclose additional behavioral traits such as data update cadence, source lag, or output detail levels.

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?

The description is a single efficient sentence that front-loads the geographic and temporal scope, then adds the case-type breakdown and prior-year context. Every phrase earns its place with no redundant wording.

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?

Given a moderate three-parameter schema, an output schema, and annotations covering safety, the description supplies the key missing context: California-only scope, fiscal year, prior-year comparison, and the 'CA' statewide option. The main minor gap is that it does not explain the response_format parameter, but that enum is largely self-explanatory.

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 low at 33%, so the description should compensate for undocumented parameters. It does explain that 'county' can be a county name or 'CA' for the whole state and that results are broken down 'by case type', which maps to the group parameter, but it omits any explanation of response_format and does not elaborate on the group enum values.

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 states a specific resource and scope: California county superior court case filings for fiscal year 2024-25, with case type and prior-year comparison. It is clear what the tool returns, but it does not explicitly name sibling tools or contrast itself with alternatives such as compare_states or get_state_market_brief.

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 'California only' and the 'CA' option establish a clear geographic usage constraint, implying when this tool is appropriate. However, it provides no explicit guidance on when to choose this tool over sibling tools that also deal with state-level data, and no exclusions beyond the California scope.

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