Skip to main content
Glama

School programs

list_programs
Read-onlyIdempotent

The school’s published program pages with live availability. Each program has a guidanceId that get_guidance accepts.

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

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.8/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 the safety profile is covered. The description adds real context beyond them: results reflect live availability, and each record carries a guidanceId consumable by get_guidance. It stops short of saying anything about ordering, pagination or cache freshness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, front-loading what the tool returns before the cross-tool linkage. Nothing is redundant with the title or annotations.

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?

With an output schema present, the description need not explain return shapes, and annotations cover safety. For a zero-required-parameter read tool the description is nearly sufficient, though a sentence on result ordering or whether all programs are returned would close the last gap.

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?

Only one parameter (language) exists and the schema documents it at 100% coverage, including the constraint that only 'en' is accepted. The description adds nothing about it, so the schema carries the full burden and the baseline 3 applies.

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 specific resource — the school's published program pages — and adds the meaningful qualifier that availability is live. It also distinguishes itself from the sibling get_guidance by explaining that the guidanceId field bridges to it. What it lacks is an explicit verb, so 'list' has to be inferred from the tool name.

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?

There is no explicit 'use this when' statement and no exclusion of siblings such as search_guidance. The one usage-relevant hint is the chaining note that get_guidance accepts a guidanceId, which implies this is the entry point for guidance lookups, but the agent must infer that sequence.

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