Skip to main content
Glama

Ca Ji Search

ca_ji_search
Read-onlyIdempotent

Find the official California jury instruction NUMBER for a claim, cause of action, or criminal charge by keyword, "breach of contract" -> CACI No. 303; "first degree murder" -> a CALCRIM number; "self-defense", "negligence", "false imprisonment". Searches official instruction/verdict-form TITLES and series names across CACI (civil), CALCRIM (criminal), or both. Returns matching numbers/titles, call caci_lookup or calcrim_lookup with a number for the full text. This is a title search, not full-text search over instruction bodies. Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "breach of contract"
    },
    "name": "ca_ji_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNoRestrict to "caci" (civil) or "calcrim" (criminal); default "both".
limitNoMax results to return, default 10, max 25.
queryYesClaim, cause of action, or charge, e.g. "breach of contract" or "first degree murder".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond that: the service is keyless, searches only official titles and series, and returns matching numbers/titles rather than instruction bodies. It does not discuss result ordering, ambiguity handling, or rate limits, so it falls short of a 5.

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?

The description is dense and front-loaded, and every clause adds routing or scope information. The semicolon-heavy example chain makes it slightly less scannable than a more structured presentation, but there is very little wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read-only search tool with no output schema, the description covers the purpose, title-only scope, upstream routing to lookup tools, authentication status, and return shape. Nothing essential for correct selection or invocation 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 query, set, and limit are already documented in the schema. The description reinforces query semantics with mappings like "breach of contract" -> CACI No. 303 and explains the civil/criminal series split, but it does not add meaning for limit behavior beyond the schema. With full schema coverage, the baseline 3 is appropriate.

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?

The description states a specific verb and resource: find the official California jury instruction number for a claim, cause of action, or charge. It limits scope to instruction/verdict-form titles and series across CACI, CALCRIM, or both, which clearly distinguishes it from lookup and full-text tools.

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

Usage Guidelines5/5

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

It explicitly says this is a title search, not full-text search over instruction bodies, and directs the agent to caci_lookup or calcrim_lookup with a number for full text. The set parameter choices for civil, criminal, or both further clarify routing between domains.

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.