Skip to main content
Glama

Caci Lookup

caci_lookup
Read-onlyIdempotent

Get the OFFICIAL text of a California Civil Jury Instruction (CACI) by number, e.g. "303" (Breach of Contract, Essential Factual Elements) or a verdict form like "VF-303". As adopted by the Judicial Council of California, current edition by default. Returns the instruction text (with bracketed/optional language as published), Directions for Use, Sources and Authority, Secondary Sources, and the revision history line ("New ...; Revised ..."). A revoked or reserved number returns status "revoked_or_reserved" with no text rather than a not-found error. ADOPTED text only, proposed revisions open for public comment are not covered. Pass edition (a prior year, e.g. a trial that occurred under an older instruction) to get that edition's text for instructions the Council flagged as changed since, only a bounded set of prior-year deltas is available (see ca_ji_editions), not a full archive. Use for "what is the official jury instruction for breach of contract" or to check the elements/Sources and Authority a civil claim instruction cites. 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": {
      "number": "303"
    },
    "name": "caci_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesCACI instruction or verdict-form number, e.g. "303", "CACI No. 303", or "VF-303".
editionNoOptional: a prior edition year (e.g. "2025") instead of the current edition. Only available where this pack has baked a delta for that number, call ca_ji_editions to see what is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / edition / description
      Previous value: -"Optional: a prior edition year (e.g. \"2025\") instead of the current edition. Only available where this pack has baked a delta for that number — call ca_ji_editions to see what is available."New value: +"Optional: a prior edition year (e.g. \"2025\") instead of the current edition. Only available where this pack has baked a delta for that number, call ca_ji_editions to see what is available."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the annotations (readOnly/idempotent/non-destructive) by disclosing the return payload section-by-section and, critically, that revoked or reserved numbers return status "revoked_or_reserved" instead of a not-found error. It also bounds the edition capability ('only a bounded set of prior-year deltas is available ... not a full archive'), which prevents a wrong expectation of archival coverage.

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?

Purpose and the key number example are front-loaded, and nearly every sentence carries operational information. It is dense rather than bloated, though the edition caveat is stated twice (inline and again in the parenthetical), which could be tightened.

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?

No output schema exists, so the description carries the return-value burden and does so fully: instruction text, Directions for Use, Sources and Authority, Secondary Sources, and revision history line. The revoked/reserved edge case and edition limitation round out what an agent needs to call and interpret this tool correctly.

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

Parameters5/5

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

Schema coverage is 100%, so 3 would be the baseline, but the description adds real meaning: `edition` is framed by the motivating scenario (a trial that occurred under an older instruction) and its limitation (only deltas baked by ca_ji_editions, verified via that sibling). `number` is shown to accept bare numbers, 'CACI No. 303', and 'VF-303' forms.

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+resource: 'Get the OFFICIAL text of a California Civil Jury Instruction (CACI) by number', with concrete example identifiers ("303", "VF-303"). It scopes the domain (civil, Judicial Council adopted text) which implicitly separates it from the criminal-instruction sibling and from the edition-metadata sibling.

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?

Explicit when-to-use phrasing ('Use for "what is the official jury instruction for breach of contract" or to check the elements/Sources and Authority'), explicit exclusions ('ADOPTED text only, proposed revisions open for public comment are not covered'), and explicit routing to ca_ji_editions before using the edition parameter.

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.