Skip to main content
Glama
Sign In

California Licensing Education

by io.github.Nathan-Roll1
OverviewDiscussionsAdmin

Court websites and next steps

find_court_information
Read-onlyIdempotent

Official superior court website and California Courts directory record for one county (the county on the citation), or all 58 when county is omitted. website is the court’s destination and sourceUrl its directory evidence. For counties with a published school guide, nextSteps links that guide’s permission, deadline and court-receipt sections; generalGuidance links the school’s general court guide; pageUpdatedAt is that page’s update date. The handling court is the one named on the citation; a city or ZIP code does not determine it. It does not look up cases, rule on eligibility or submit anything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_court_information"
  }
}

Input Schema

NameRequiredDescriptionDefault
countyNo
languageNoInformation language code. Only en is accepted; omit it to use the default.en

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / meta / properties / offer
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "available": {
+          "const": false,
+          "type": "boolean"
+        },
+        "courtFeesIncluded": {
+          "const": false,
+          "type": "boolean"
+        },
+        "feeTiming": {
+          "type": "null"
+        },
+        "freeStartEnabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "pricing": {
+          "type": "null"
+        },
+        "sourceUrl": {
+          "const": "https://traffic.californialicensingeducation.com/api/v1/school",
+          "type": "string"
+        }
+      },
+      "required": [
+        "courtFeesIncluded",
+        "sourceUrl",
+        "available",
+        "freeStartEnabled",
+        "pricing",
+        "feeTiming"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "available": {
+          "const": true,
+          "type": "boolean"
+        },
+        "courtFeesIncluded": {
+          "const": false,
+          "type": "boolean"
+        },
+        "feeTiming": {
+          "const": "before-final-exam",
+          "type": "string"
+        },
+        "freeStartEnabled": {
+          "const": true,
+          "type": "boolean"
+        },
+        "pricing": {
+          "additionalProperties": false,
+          "properties": {
+            "basic": {
+              "maximum": 9007199254740991,
+              "minimum": 0,
+              "type": "integer"
+            },
+            "currency": {
+              "const": "USD",
+              "type": "string"
+            }
+          },
+          "required": [
+            "basic",
+            "currency"
+          ],
+          "type": "object"
+        },
+        "sourceUrl": {
+          "const": "https://traffic.californialicensingeducation.com/api/v1/school",
+          "type": "string"
+        }
+      },
+      "required": [
+        "courtFeesIncluded",
+        "sourceUrl",
+        "available",
+        "freeStartEnabled",
+        "pricing",
+        "feeTiming"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "available": {
+          "const": true,
+          "type": "boolean"
+        },
+        "courtFeesIncluded": {
+          "const": false,
+          "type": "boolean"
+        },
+        "feeTiming": {
+          "const": "before-enrollment",
+          "type": "string"
+        },
+        "freeStartEnabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "pricing": {
+          "additionalProperties": false,
+          "properties": {
+            "basic": {
+              "maximum": 9007199254740991,
+              "minimum": 0,
+              "type": "integer"
+            },
+            "currency": {
+              "const": "USD",
+              "type": "string"
+            }
+          },
+          "required": [
+            "basic",
+            "currency"
+          ],
+          "type": "object"
+        },
+        "sourceUrl": {
+          "const": "https://traffic.californialicensingeducation.com/api/v1/school",
+          "type": "string"
+        }
+      },
+      "required": [
+        "courtFeesIncluded",
+        "sourceUrl",
+        "available",
+        "freeStartEnabled",
+        "pricing",
+        "feeTiming"
+      ],
+      "type": "object"
+    }
+  ]
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: omitting county fans out to all 58 records, and it defines the relationship between website and sourceUrl plus what nextSteps and generalGuidance link to. It does not describe result size or paging for the all-counties case, which is the main remaining gap.

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?

It is front-loaded with the resource and scope, then the field semantics, then the negative boundary, which is a sensible order. The dense sentence enumerating nextSteps, generalGuidance and pageUpdatedAt is somewhat redundant against the output schema, but each clause still carries meaning.

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 lookup with an output schema and full annotations, the definition covers the ambiguous parts: what county means, the all-counties default, and what it does not do. The only shortfall is the absence of any indication of result volume or shape when county is omitted.

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

Parameters4/5

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

Schema coverage is only 50% — county has no description in the schema — and the description compensates by defining exactly what county means (the county on the citation), warning that city or ZIP does not determine it, and stating that omission returns all 58. The language parameter is already documented as en-only in the schema, so the description rightly does not repeat it.

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 opens with a specific verb-plus-resource framing: it returns the official superior court website and California Courts directory record for a single county, or all 58 when county is omitted. That scope statement, together with the handling-court rule, makes it clearly distinct from siblings like get_eligibility_checklist or get_guidance 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?

It gives concrete usage context — pass the county named on the citation, omit county to get all 58 — and explicit exclusions: it does not look up cases, rule on eligibility, or submit anything. It never names the sibling that handles eligibility, so the routing is implied by topic rather than stated outright.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All California Licensing Education toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources