Skip to main content
Glama

list_rule_sets

Read-only

List every deadline rule set 1Court covers, with rule counts and scope. Coverage: Deadlines: California in depth (civil, family, probate, eviction, small claims, government claims, criminal, juvenile, appeals, agencies, pre-suit clocks, special proceedings, statutes of limitations; local rules for all 58 counties), federal civil and criminal, federal bankruptcy, and a partial Texas set. Other states’ deadlines are not covered. Court directory: every U.S. county. Use the rule_set ids with search_rules, get_rule and calculate_deadline.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_rule_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value with the jurisdictional coverage boundary and the fact that counts and scope come back per set, but it says nothing about ordering, pagination, or how many sets to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the follow-up instruction are front-loaded and earn their place, but the middle is a long enumerated list of California practice areas and all 58 counties that reads as marketing copy. Condensing it to "California in depth, federal civil/criminal/bankruptcy, partial Texas" would convey the same decision-relevant information.

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?

For a zero-parameter read-only catalog tool with no output schema, the description covers what is returned (rule sets with counts and scope) and what to do with the ids. Nothing essential is missing, though the return shape is described only in prose.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the note about reusing returned rule_set ids is a bonus rather than a parameter explanation.

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 first sentence gives a specific verb and resource ("List every deadline rule set") plus the returned fields (rule counts and scope). It is distinguishable from siblings such as list_states or list_counties, though it never explicitly contrasts itself with the similarly named list_deadline_rules.

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 states the downstream path clearly: take rule_set ids into search_rules, get_rule, and calculate_deadline. The coverage paragraph also functions as a when-not-to-use signal ("Other states' deadlines are not covered"), but there is no direct comparison to the closest sibling, list_deadline_rules.

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