Skip to main content
Glama

Read public guidance

get_guidance
Read-onlyIdempotent

One reviewed guidance answer by ID (from search_guidance, availableGuidanceIds or list_programs), with its source URLs, review date and the school’s live availability. An answer may be a short summary; open its linked school page for the complete page. Answers summarize cited pages as of their review date; they are not a fresh source check.

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": {
      "id": "<id>"
    },
    "name": "get_guidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
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.7/5.0
Behavior5/5

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

Annotations already declare this a safe, idempotent read, so the description's added value is the currency caveat: answers are summaries as of a review date and are "not a fresh source check." It also discloses that a field can mix static reviewed content with live school availability, which is a non-obvious behavioral trait an agent could otherwise misread.

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?

Three sentences, none wasted: the payload comes first, then the recovery path for truncated answers, then the freshness caveat. The front-loading puts the identifying information before the caveats.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Return values need not be detailed because an output schema exists, and the description covers the remaining risks: summary truncation, snapshot staleness, and the need for provenance-correct IDs. Nothing an agent needs in order to call this correctly is missing.

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%, with id carrying no schema description at all, so the description must compensate. It does so by specifying the provenance of the ID, which tells the agent how to obtain a valid value; the language parameter is documented in the schema instead.

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 and resource ("One reviewed guidance answer by ID") and enumerates the returned payload (source URLs, review date, live availability), which no sibling tool provides. It also names the producer tools that yield valid IDs, so the agent can distinguish it from search_guidance at a glance.

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 explicitly routes the agent to the correct ID sources ("from search_guidance, availableGuidanceIds or list_programs") and tells the agent what to do when the answer is only a summary ("open its linked school page"). It stops short of stating when not to use it, e.g. that search_guidance should be preferred when no ID is known, but the practical guidance is clear.

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