Skip to main content
Glama

get_driving_school_options

Check South African K53 Code 8 driving school package pricing (R1,900-R6,500), live local suburb pickup coverage across Pretoria, Centurion, Midrand, and nationwide cities, and required booking fields before submitting a free callback enquiry.

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_driving_school_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoTarget South African city or town (e.g., 'Pretoria', 'Centurion', 'Midrand', 'Johannesburg', 'Cape Town', 'Durban')
suburbNoSpecific suburb or pickup area (e.g., 'Waterkloof', 'Montana', 'Irene', 'Waterfall')
transmissionNoPreferred Code 8 gearbox transmission ('manual' or 'automatic')
booked_by_roleNoWhether the booking is for the learner themselves ('learner') or by a parent/sponsor for their child ('parent')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. 'Check' and the mention of 'live' coverage imply a non-mutating, read-only lookup and suggest the data is fetched rather than cached, but the description never states there are no side effects, how fresh the pricing is, or whether results are scoped by region.

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?

A single sentence with the action front-loaded and the three lookups (pricing, coverage, booking fields) enumerated in a parallel list. It is dense but every clause carries substance; the parenthetical price range and city list are informative rather than padding.

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 lookup tool with no required parameters, a fully documented schema, and no output schema, the description covers what will be returned (price band, coverage, required booking fields) and its place in the flow. Absent an output schema, more detail on the response shape would be the only remaining 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?

Schema description coverage is 100% with two of four parameters enum-constrained, so the schema already explains city, suburb, transmission, and booked_by_role fully. The description's mention of 'booking fields' and city names adds framing but no meaning beyond what the schema documents, so 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 opens with a specific verb ('Check') and a concrete resource (South African K53 Code 8 driving school package pricing, pickup coverage, booking fields), so an agent knows exactly what this tool returns without opening the schema. It is only partially differentiated from siblings, since it references a 'free callback enquiry' but never names request_driving_school_callback or build_driving_school_booking_link as the follow-on tools.

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?

The phrase 'before submitting a free callback enquiry' implies this is a read-only pre-flight step preceding a write/enquiry action, which is useful sequencing context. However, no alternative tool is named explicitly and there is no statement of when this tool should not be used (e.g., when the learner already knows the package).

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