Skip to main content
Glama

Ca Code Section

ca_code_section
Read-onlyIdempotent

Get the FULL TEXT of a section of the California Codes — California state statutes — by citation. "Penal Code 187" is code "PEN", section "187". Returns the statutory text, where it sits in the code, and when it was last amended. Served from a stored copy of the official California legislative code database, with the data date in every answer. Keyless. Use for "what does California Penal Code 187 say", "text of California Civil Code 1542", or to check a California statute a contract or case relies on.

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": {
      "code": "PEN",
      "section": "187"
    },
    "name": "ca_code_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesCalifornia code abbreviation, e.g. "PEN" (Penal), "CIV" (Civil), "VEH" (Vehicle), "LAB" (Labor). Call ca_codes to see all 29.
sectionYesSection number as cited, e.g. "187" or "1542". Subdivisions like "187(a)" are not separate documents — pass the section.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely new operational context: results come from a stored copy of the official legislative database rather than a live query, the data date is included in every answer, and no API key is required — which matters because 'openWorldHint' would otherwise suggest live lookup.

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 core verb and resource, then citation format, then return contents, then provenance and use cases — a sensible order. It is denser than strictly necessary (the citation restatement appears twice) but no sentence is filler.

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?

There is no output schema, and the description compensates by enumerating what comes back: statutory text, position in the code, last-amended date, and the data vintage. For a two-parameter read-only lookup this leaves nothing an agent needs 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 coverage is 100% and both parameters are already well documented in the schema, including the note that subdivisions like '187(a)' are not separate documents. The description reinforces the citation-to-parameter mapping with a worked example but adds little the schema does not already say, so the baseline of 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?

States a specific verb and resource — 'Get the FULL TEXT of a section of the California Codes' — and immediately disambiguates the citation format ('"Penal Code 187" is code "PEN", section "187"'). It is clearly distinguishable from the sibling ca_codes, which it names as the place to look up abbreviations.

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?

Provides concrete use cases in quoted form ('what does California Penal Code 187 say', checking a statute a contract or case relies on) and routes to ca_codes for the abbreviation list. It does not state an explicit when-not condition, but the applicable scope is unambiguous for a lookup tool.

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.