Skip to main content
Glama

Court permission checklist

get_eligibility_checklist
Read-onlyIdempotent

Steps for confirming traffic-school permission with the court: the deadline, separate court fees, choosing a licensed school, and confirming the court received the completion. It lists what to check with the court; it is not an eligibility decision.

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": "get_eligibility_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds meaningful behavior beyond that: the output is a static list of things to verify with the court rather than a personalized determination, which sets the right expectation for how to interpret results. An output schema exists, so return-shape detail is correctly omitted.

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?

The purpose is front-loaded in the first clause and the whole definition is two sentences with no filler. The content enumeration is slightly run-on, but every phrase carries information the agent needs to judge relevance.

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 read-only, no-required-parameter checklist tool with full annotation coverage and an output schema, the description is sufficient: it says what the checklist contains and what it does not decide. The only residual gap is the missing pointer to the sibling tool an agent should use instead when an actual eligibility decision is needed.

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?

There is a single parameter and schema description coverage is 100% — the schema states that only 'en' is accepted and that omitting it uses the default. The description adds nothing about the language parameter, so it lands at the baseline for a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the concrete resource — a checklist of steps for confirming traffic-school permission with the court — and enumerates its contents (deadline, separate court fees, choosing a licensed school, confirming completion was received). It does not differentiate itself from siblings such as get_guidance, search_guidance, or find_court_information, even though their names suggest overlapping territory.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It supplies one useful exclusion: 'it is not an eligibility decision,' which tells the agent not to use it for determinations. However, no positive trigger (e.g., 'call this when a student asks what to do to get court approval') is stated and no alternative tool is named for the eligibility-decision case, so routing must be inferred.

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.

Resources