Skip to main content
Glama

search_rules

Read-only

Find deadline rules by plain words (for example "opposition to motion", "answer complaint", "notice of appeal"). Searches rule names, ids, citations and triggers. Optionally limit to one rule_set (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). Returns up to 20 rules with their rule_set, rule_id and rule page URL; use get_rule or calculate_deadline next.

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": {
      "query": "<query>"
    },
    "name": "search_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWords describing the deadline, e.g. "opposition to motion" or "CCP 1005"
rule_setNoOptional rule 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

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the result cap (up to 20 rules) and the returned fields (rule_set, rule_id, rule page URL) — important since there is no output schema. It does not say how results are ranked or whether an empty result means the terms were too narrow.

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?

A single front-loaded sentence block: purpose and query examples come first, then the optional filter, then the return contract and next steps. The only inefficiency is re-enumerating all 17 rule_set ids that the schema already lists, which lengthens without adding 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 two-parameter read-only search with no output schema, it covers the searchable fields, the filter, the result cap and the return shape, plus the follow-up tools. The remaining gap is behavior on failure or empty results, which an agent would want before retrying.

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 coverage is 100%, so the baseline is 3; both parameters are already fully documented in the schema. The description contributes only illustrative query phrasing and a restatement of the rule_set value list, adding little meaning beyond the structured fields.

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 ("Find deadline rules") and immediately narrows scope by listing what is searched (rule names, ids, citations, triggers) with concrete query examples. An agent can distinguish it from get_rule and calculate_deadline without opening any schema.

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?

Explicitly routes the agent onward: "use get_rule or calculate_deadline next", which clarifies this is the discovery step in a two-stage flow. It does not explain when to prefer it over the sibling list_deadline_rules or what to do when the query returns nothing, so a full 5 is not warranted.

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