Skip to main content
Glama

get_rule

Read-only

Get one deadline rule: its period, trigger, citation, the verbatim rule text, the official source URL, the 1Court rule page, any disclosed alternate reading (safe-date policy) and any fixed statutory dates. Show the user the citation and source link with every date or rule. 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": {
      "rule_set": "<rule_set>",
      "rule_id": "<rule_id>"
    },
    "name": "get_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNoCourt id for local rules (cacd, cand, casd, caed, ca9, cacb, canb, casb, caeb, 1dca to 6dca)
countyNoCalifornia county slug, to include that county’s local rules
rule_idYesRule id from search_rules or list_deadline_rules
rule_setYesRule set id: TX, CA, CA-FAM, CA-APP, US, US-BK, US-CRIM, CA-PROB, CA-UD, CA-SC, CA-GOV, CA-CRIM, CA-JUV, CA-AGENCY, CA-PRESUIT, CA-SPECIAL, CA-SOL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description goes beyond them by disclosing the shape of the payload — verbatim rule text, official source URL, alternate safe-date reading, fixed statutory dates — which tells the agent how to attribute and caveat results. It adds a display obligation and a "not legal advice" disclaimer that matter for how the agent relays output. It does not say what happens when a rule_id or rule_set is unknown, which is the main remaining behavioral gap.

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

Conciseness4/5

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

Front-loaded with the verb and resource, then the payload inventory, then two short imperative directives. The middle sentence is a long comma-list that is slightly dense but every item is substantive content, not filler. Nothing is redundant with the annotations or schema.

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?

There is no output schema, so the description carries the burden of telling the agent what a result looks like, and it does so field by field while also flagging the alternate reading and the disclaimer. Combined with 100% schema coverage on inputs, an agent can call this correctly. Missing only failure/empty-result behavior for a bad rule_id.

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% and all four parameters are documented there, including the enumerated court ids and rule set ids, so the description adds no parameter-level meaning. Baseline 3 applies. The one nuance the description could have supplied — that court/county are optional local-rule scoping on top of a required rule_set + rule_id — is left to the schema.

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?

"Get one deadline rule" gives a specific verb plus resource, and the rest of the sentence enumerates exactly what comes back (period, trigger, citation, verbatim text, source URL, 1Court page, alternate reading, fixed statutory dates). That is far more specific than a generic "get rule". It does not name a sibling to contrast with, so the agent must infer that search_rules/list_deadline_rules are the discovery tools and this is the retrieval-by-id tool.

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 description implies retrieval of a single already-identified rule, and the schema's rule_id field points back to search_rules/list_deadline_rules as the source of that id. However, it never states when to use this versus calculate_deadline (which presumably applies the rule to a date) or get_court_info, and gives no prerequisites. The only explicit directives are presentation rules ("show the user the citation and source link"), not selection guidance.

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