ca-rate-filings

Search Filings

search_filings

Read-onlyIdempotent

Search the SERFF filings corpus by carrier, NAIC, product line, state, year-range, filing type, or bureau lineage. Returns a lite row shape per match (SERFF id, state, year, NAIC, group code, carrier name, product name, filing type / status / date). For the substance of a filing, follow up with get_filing_summary once you have a SERFF id.

All filters AND together. Defaults: limit=25, capped at 100; ordered by filing date descending. Pagination via offset. The full count matching the predicate is returned in total (independent of limit/offset) so you can decide whether to paginate or narrow the predicate.

Common patterns:

"All California auto filings from 2024" → state="CA", product_type="Auto", year=2024.
"Recent rule changes in workers comp" → product_type="Workers", filing_type="Rule", year_from=2023.
"Which Progressive filings adopted ISO?" → search="PRGS", predecessor_prefix="ISOF".
"Anything mentioning telematics in the product name" → search="telematics".

predecessor_prefix answers "filings adopted from a bureau" questions — it restricts to filings that appear in some programme's adopted-from chain, so orphan bureau filings no carrier ever pulled in are excluded. Validated against /^[A-Z][A-Z0-9]{1,7}-?$/; trailing dash optional. Invalid values return { error: ... } rather than a row set.

Only filings that have been fully read and classified are returned — partial / pre-classification rows are hidden so every result is a filing you can actually reason about.

Input Schema

TableJSON Schema

Name	Required	Description
`naic`	No	Exact match on the NAIC carrier identifier (5-digit string). Use when you know the specific carrier (e.g. "24260" = Progressive Direct). One filing always belongs to exactly one NAIC.
`year`	No	Exact filing year (e.g. 2024). The corpus covers filings from 2005 onward; earlier years return no rows. Mutually exclusive with `year_from`/`year_to` — pick one form.
`limit`	No	Max rows returned in this call. Defaults to 25; capped at 100. Pair with `offset` to page. Always check `total` in the response to decide whether you need more pages.
`state`	No	Two-letter US state code, uppercase. The corpus currently covers California (`CA`) only — other state codes will return no rows until additional states are onboarded. One filing always belongs to exactly one state.
`offset`	No	Row offset for pagination. Defaults to 0. Combined with the descending filing-date ordering, `offset=N` skips the most recent N filings matching the predicate.
`search`	No	Free-text wildcard match across SERFF id, carrier name, and product name. Useful for "anything mentioning Progressive" or "filings whose product name contains 'condo'". Prefer the structured fields below — `naic`, `state`, `filing_type`, `product_type` — when you can; they are more precise and do not false-match on substrings.
`date_to`	No	Upper bound on filing date as ISO date (YYYY-MM-DD).
`year_to`	No	Upper bound on filing year, inclusive.
`date_from`	No	Lower bound on filing date as ISO date (YYYY-MM-DD). Use for finer-grained windows than `year_from` allows. Compares against the date the carrier submitted the filing, not the rate effective date.
`year_from`	No	Lower bound on filing year, inclusive. The corpus covers filings from 2005 onward. Pair with `year_to` for a range, or use alone for "everything since".
`filing_type`	No	Wildcard match on filing type. Common values: "Rate", "Rule", "Rate/Rule", "Loss Cost / Rule", "Form", "Rate/Rule/Form", "Withdrawal", "Correspondence", "Adoption". Substring matches: `filing_type="Rule"` returns Rule, Rate/Rule, and Loss Cost / Rule. Substantive (rate-affecting) filings are typically Rate, Rule, Rate/Rule, Loss Cost / Rule, or Form combinations.
`product_type`	No	Wildcard match on product type. Common values include "Personal Auto", "Homeowners", "Commercial Auto", "Workers Compensation", "Property", "Liability". Substring matches: `product_type="Auto"` returns Personal Auto and Commercial Auto.
`predecessor_prefix`	No	Bureau or organisation SERFF prefix — common values: "ISOF" (ISO Services), "NCCI" (workers comp loss costs), "AAIS" (American Association of Insurance Services), "MSO" (Mutual Service Organisation). Returns filings carriers actually adopted into a programme — orphan bureau filings nobody picked up are excluded. Validated against /^[A-Z][A-Z0-9]{1,7}-?$/ (1-8 alphanumeric chars, trailing dash optional). Invalid input returns `{ error: ... }`. Case-insensitive on the way in.

TDQS

A5/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds: all filters AND together, default/capped limit, descending order, pagination via offset, total count independent of limit/offset, validation of predecessor_prefix with error response, and that only fully read/classified filings are returned. This gives comprehensive behavioral context.

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 well-structured with clear sections: purpose, behavior, common patterns, special parameter details, and data readiness. Each sentence adds value, and it is front-loaded with the core purpose. Despite length, it is efficient and not verbose.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 13 parameters, no output schema, and 16 siblings, the description is complete: it explains input, behavior, pagination, error handling, common patterns, and the return shape (lite row with specific fields). It also clarifies that partial filings are hidden. No gaps for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning: common patterns for each parameter, mutual exclusivity of year vs year_from/to, wildcard matching behavior for filing_type and product_type, and precise explanation of predecessor_prefix. This goes well beyond the schema alone.

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 clearly states the tool searches the SERFF filings corpus by various criteria and returns a lite row shape, explicitly distinguishing from get_filing_summary for substance. The verb 'Search' and resource 'SERFF filings corpus' are specific, and it differentiates from siblings as a search/discovery tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance: follow up with get_filing_summary for details, prefer structured fields over free-text, and includes common patterns like 'All California auto filings from 2024'. It tells when to use this tool and when to narrow or paginate, but does not explicitly contrast all siblings; however, the guidance is sufficient.

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

All ca-rate-filings tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation4/5

The get_filing_* family has distinct purposes, though get_filing_lineage and get_filing_references could be confused without the detailed descriptions. The search_* tools are clearly separated by embedding surface, and dossier/composite vs single-filing retrievals are explicitly differentiated.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern with clear prefixes: get_filing_*, search_*, list_*, and mcp_*. No style mixing or vague generic verbs.

Tool Count4/5

At 16 tools, this sits at the upper edge of the ideal range. Each tool earns its place, though get_filing_dossier could have been a client-side composition of the other get_filing_* calls rather than a separate tool.

Completeness5/5

The domain (retrieving CA rate filings) is covered end to end: structured and semantic search across multiple granularities, filing summaries, correspondence threads, actuarial numerics, lineage, source file listing/download, and reviewer caseload. The read-only nature of the domain means no create/update operations are needed, and every retrieval path leads to a terminal artifact.

Resources

Need Help?