California Licensing Education

Compare insurance scenarios and school costs

calculate_insurance_comparison

Read-onlyIdempotent

Compares two premiums the user supplies for the same coverage over a chosen number of months, then adds the user’s school, court and optional costs. Returns prorated totals, their difference and a break-even month. Amounts are integer US cents; the tool does not estimate premiums, surcharges, durations or fees, is not an insurance quote or prediction, and excludes the citation fine common to both scenarios. Its inputs are amounts only; names, policy numbers and ticket details are not part of them.

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": {
      "baselinePremiumCents": "<baselinePremiumCents>",
      "comparisonPremiumCents": "<comparisonPremiumCents>",
      "premiumPeriodMonths": "<premiumPeriodMonths>",
      "comparisonMonths": "<comparisonMonths>",
      "tuitionCents": "<tuitionCents>",
      "courtSchoolFeeCents": "<courtSchoolFeeCents>",
      "optionalFeesCents": "<optionalFeesCents>"
    },
    "name": "calculate_insurance_comparison"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Information language code. Only en is accepted; omit it to use the default.	en
`tuitionCents`	Yes
`comparisonMonths`	Yes
`optionalFeesCents`	Yes
`courtSchoolFeeCents`	Yes
`premiumPeriodMonths`	Yes
`baselinePremiumCents`	Yes	User-supplied baseline premium for the selected policy period.
`comparisonPremiumCents`	Yes	User-supplied alternative premium for the same coverage and policy period.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

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"
+    }
+  ]
+}

First observedNov 6, 2026

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, closed-world behavior, so the description's job is additive. It adds real value beyond them: amounts are integer US cents, the tool computes rather than estimates, inputs are amounts only (no names, policy numbers, ticket details), and the citation fine is excluded from both scenarios.

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?

Two sentences, front-loaded with what the tool computes and returns before the constraints. The trail of negations is dense but each one guards against a plausible misuse (treating it as a quote or estimator), so little is wasted.

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, so return values need not be explained, and the description still summarizes them along with units. For an 8-parameter calculation tool the main remaining gap is that several required numeric fields carry no semantic explanation in either the schema or the description.

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?

With only 38% schema description coverage, the description must compensate, and it does partially: the two premiums are clarified as user-supplied for the same coverage over a chosen period, and tuition/court/optional costs are identified as add-ons, with cents stated as the unit. It does not disambiguate premiumPeriodMonths versus comparisonMonths or explain what each fee field covers, leaving some gaps.

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 names a specific verb (compares) and resources (two user-supplied premiums plus school, court and optional costs) and states what it returns: prorated totals, their difference, and a break-even month. No sibling tool in the list performs calculation, so the contrast is unambiguous without needing an explicit callout.

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 clear negative guidance — it does not estimate premiums, surcharges, durations or fees, is not a quote or prediction, and excludes the shared citation fine — which tells an agent what not to expect from it. It stops short of explicitly naming when to choose it over siblings or which sibling to use for the excluded fine, so it lands at 4 rather than 5.

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?