California Licensing Education

Search public guidance

search_guidance

Read-onlyIdempotent

Search the school’s reviewed public guidance on California traffic school: licensing, school and court costs, court fees by county, eligibility and the 18-month rule, deadlines and extensions, points and insurance, completion reporting, commercial licenses, and county court steps. Returns navigational topic IDs, titles and exact article URLs; reviewed answers and complete source lists are supplied by get_guidance. Empty results include availableGuidanceIds listing every article. Contains no course lessons or exam content.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_guidance"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`language`	No	Information language code. Only en is accepted; omit it to use the default.	en

Output Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedOutput schema / properties / data / properties / details / properties / note / const

Previous value: -"Retrieve by id for the complete reviewed answer and source list before answering. The linked school page may contain more."New value: +"Retrieve by id for the reviewed answer and full sources before answering. The page may contain more. Current offer: get_school_status."

First observedNov 6, 2026

TDQS

A4/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 still adds real behavior beyond them: the return shape (topic IDs, titles, exact article URLs) and the empty-result fallback where availableGuidanceIds lists every article — a non-obvious recovery path an agent would otherwise miss.

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 scope are front-loaded in the first sentence, with return behavior and the get_guidance handoff following. The long topical enumeration is dense but earns its place by telling the agent what is in scope; a few clauses could be tightened.

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?

An output schema exists, yet the description still usefully frames the returns as navigational rather than authoritative, and it covers the empty-result case and the handoff to get_guidance. The main remaining gap is query/limit semantics, which leaves the tool slightly under-specified for a 3-parameter search.

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

Parameters2/5

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

Schema description coverage is only 33% — only 'language' is documented in the schema. The description says nothing about what 'query' should contain (keywords vs. natural language), what 'limit' controls, or that it is capped at 10, so the undocumented parameters remain opaque in both places.

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?

Names a specific verb and resource ('Search the school's reviewed public guidance') and enumerates the covered topic domains (licensing, costs, eligibility, 18-month rule, points, completion reporting). It also distinguishes itself from get_guidance by stating that search returns navigational IDs/titles/URLs while get_guidance supplies reviewed answers and source lists.

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?

Clearly establishes the search-then-read workflow by pointing to get_guidance for answers and source lists, and adds an exclusion ('contains no course lessons or exam content') that routes the agent away from course/exam tooling. It stops short of an explicit 'use this when / do not use this when' formulation, so it is strong but not exhaustive.

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 tools Inspect

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

Need Help?