CT Injury Cases

Case statistics

stats

Read-onlyIdempotent

Compute one metric over cases (or motion rulings), optionally broken down by up to two dimensions and narrowed by filters. describe_dataset lists every metric and dimension and which unit each applies to. Groups of three or fewer cases are suppressed. At most 100 groups, largest first.

Input Schema

Name	Required	Description
`metric`	Yes	What to compute; see describe_dataset for each metric.
`um_uim`	No	UM/UIM coverage is claimed.
`purpose`	No	One sentence on what you are trying to find out. Logged to improve the dataset; never returned.
`district`	No	Judicial district, e.g. HARTFORD JD.
`filed_to`	No	Filed on or before this date (YYYY-MM-DD).
`group_by`	No	Up to two dimensions to break the metric down by.
`case_type`	No	Case type code: V01, V04 or V09.
`judge_key`	No	Judge key from search_judges; matches the judge who decided the disposition.
`mechanism`	No	How the crash happened, e.g. rear_end.
`road_type`	No	Kind of road, e.g. interstate.
`filed_from`	No	Filed on or after this date (YYYY-MM-DD).
`trial_kind`	No	jury, court or not_tried.
`injury_kind`	No	An alleged injury kind, e.g. fracture.
`injury_region`	No	An injured body region, e.g. neck.
`plaintiff_role`	No	driver, passenger, pedestrian…
`litigation_type`	No	third_party, um_uim or subrogation.
`amount_in_demand`	No	Amount-in-demand band, e.g. 15000_or_more.
`claims_lost_wages`	No	Lost wages are claimed.
`firm_juris_number`	No	Juris number from search_firms; matches either side's lead firm.
`commercial_vehicle`	No	A commercial vehicle was involved.
`disposition_category`	No	How the case ended, e.g. withdrawal or plaintiff_verdict; pending for open cases.

Output Schema

Name	Required	Description
`unit`	Yes	What the metric counts: cases, or motion rulings for motion_grant_rate.
`names`	Yes	Names of the judges and firms in the groups.
`groups`	Yes	One entry per group, largest n first.
`metric`	Yes	The metric computed.
`groupBy`	Yes	The group_by dimensions, in order.
`closedTo`	Yes	For metrics over closed cases, the last disposition date counted, inclusive: the as-of date. Null for metrics over every case.
`truncated`	Yes	True when more groups exist than were returned.
`closedFrom`	Yes	For metrics over closed cases, the first disposition date counted, inclusive; the figures are not all-time. Null for metrics over every case.
`totalGroups`	Yes	Groups before the cap on how many are returned.
`groupsSuppressed`	Yes	Returned groups that are suppressed.
`multiValuedDimensions`	Yes	Dimensions where one case can sit in several groups, so group counts overlap.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world safety, but the description adds genuinely non-obvious behavior: small-group suppression (three or fewer cases), a 100-group cap, and largest-first ordering. These are exactly the traits an agent cannot infer from the schema, though it doesn't say what an invalid metric/unit combination returns.

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?

Four sentences, each earning its place: purpose first, then the discovery pointer, then the two limits. No filler and no repetition of schema content.

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?

With 21 parameters, an output schema, and rich annotations, the description covers the things structured data can't: suppression, group cap, ordering, and where to learn valid metrics. Only a note on how filters interact with the case-vs-motion unit distinction is missing.

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 100%, so the schema already carries parameter meaning and a 3 is the baseline. The description only restates that grouping takes up to two dimensions and that filters narrow results, adding nothing beyond maxItems and the per-field descriptions.

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?

States a specific verb and resource ("Compute one metric over cases (or motion rulings)") plus the two modifiers available (grouping dimensions and filters). This clearly separates it from retrieval siblings like search_cases and get_case, which return individual records rather than aggregates.

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

Usage Guidelines4/5

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

It routes the agent to describe_dataset for metric/dimension enumeration and states which unit each metric applies to, which is real usage guidance. However, it never states when to choose this over search_cases plus manual counting, nor any prerequisite conditions or exclusions.

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

All CT Injury Cases tools Inspect

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

Need Help?