Skip to main content
Glama

Court Rules

by app.courtrules
OverviewDiscussionsAdmin

Server Details

Judge-level filing rules, court holidays and enforcement data for US federal and state courts.

Ownership verified

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
61.3% over 43 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation4/5

Most tools are clearly distinct: compliance check, enforcement details/stats/search, judge rules, court holidays, courts list, filing rules, judge search. The only slight overlap is get_enforcement_details vs search_enforcement_actions, but the former is for a specific action's full details while the latter is a filtered search, so they are reasonably distinguishable.

Naming Consistency4/5

Tool names mostly follow a consistent verb_noun pattern: check_compliance, get_enforcement_details, get_enforcement_stats, get_judge_rules, list_court_holidays, list_courts, search_enforcement_actions, search_filing_rules, search_judges. The pattern is consistent (list_/get_/search_/check_), with no mixed casing or chaotic naming.

Tool Count5/5

9 tools is well within the ideal 3-15 range. Each tool covers a distinct aspect of court rules and enforcement data, and none feel redundant or unnecessary.

Completeness4/5

The set covers searching courts, judges, filing rules, enforcement actions, and court holidays, plus compliance check generation. Minor gaps: no tool for retrieving a specific court's full details beyond the list, and no tool for retrieving a specific filing rule by ID, but agents can likely work around these with search tools.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedsearch_judges1 field changed
      • addedInput schema / properties / include_inactive
        Added value: +{
+  "description": "Include judges who no longer sit in the court's published roster. Off by default: these carry no current rules.",
+  "type": "boolean"
+}
  2. 9 tool updates
    • First observedcheck_compliance
    • First observedget_enforcement_details
    • First observedget_enforcement_stats
    • First observedget_judge_rules
    • First observedlist_court_holidays
    • First observedlist_courts
    • First observedsearch_enforcement_actions
    • First observedsearch_filing_rules
    • First observedsearch_judges

Related MCP Connectors

Related MCP Servers

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