Skip to main content
Glama

Ca Ji Editions

ca_ji_editions
Read-onlyIdempotent

List the CURRENT edition year/adoption date and ARCHIVED edition PDF links for CACI (civil) and/or CALCRIM (criminal) jury instructions. Use when a caller needs a past year's edition (e.g. for a trial that occurred under an older version) or just wants to confirm which edition caci_lookup/calcrim_lookup text comes from. Archived editions are LINKED, not text-extracted, only the current edition's instruction text is available via caci_lookup/calcrim_lookup. 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": {
      "set": "both"
    },
    "name": "ca_ji_editions"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNoRestrict to "caci" (civil) or "calcrim" (criminal); default "both".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, and the description adds real context beyond that: no key is required, and archived editions are links rather than searchable text. It does not say what happens when no archived edition exists or what the link payload looks like, which keeps it just 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.

Conciseness5/5

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

Three tight sentences with the core capability front-loaded, followed by the usage trigger and then the critical limitation. Every sentence carries distinct information and nothing is repeated from the title or annotations.

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 single-optional-parameter listing tool with no output schema, the description covers what is returned (edition year, adoption date, archived PDF links), how archived content differs from current text, and the keyless access. Nothing needed to invoke it correctly 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?

Only one optional parameter exists and its schema description already documents the enum values and the 'both' default (100% coverage). The description's 'and/or' phrasing and the CACI (civil)/CALCRIM (criminal) gloss reinforce the enum but add no new syntax or format detail, so the baseline 3 applies.

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: it lists current edition year/adoption date plus archived edition PDF links for CACI and/or CALCRIM. It also names the sibling tools (caci_lookup/calcrim_lookup) whose text it complements, so an agent can separate it from the lookup tools 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 Guidelines5/5

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

Gives an explicit trigger: when a caller needs a past year's edition, e.g. a trial that occurred under an older version, or wants to confirm which edition the lookup text comes from. It also states the exclusion clearly: archived editions are linked, not text-extracted, and only the current edition's text is available through caci_lookup/calcrim_lookup.

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.