Skip to main content
Glama

MyLearners K53 Co-Pilot — SA Learner Licence Exam Prep

build_driving_school_booking_link

Generate a pre-filled MyLearners 3-step driving school callback URL with role, package, transmission, city, and suburb pre-selected (contains zero personal phone/email PII in the URL).

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity or town for driving lessons (e.g., 'Pretoria', 'Centurion', 'Midrand')
suburbNoPickup suburb or area (e.g., 'Waterkloof', 'Irene', 'Waterfall')
transmissionNoPreferred Code 8 vehicle transmission ('manual' or 'automatic')
booked_by_roleNoWho is enquiring: 'learner' (myself) or 'parent' (parent/sponsor for my child)
package_interestNoPackage tier: 'practical_lessons' (R1,900-R5,500 Practical + Test Car) or 'full_package' (R5,500-R6,500 Full Learner's + Driver's Package)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose one genuinely useful behavioral fact, that the generated URL contains zero phone/email PII, and identifies the destination as a 3-step MyLearners flow. It does not say whether the call has any side effects, whether the link expires, or whether omitted fields are left blank or defaulted.

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?

A single front-loaded sentence with no filler; the artifact being produced comes first and the supporting detail follows. Nothing could be removed without losing information.

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 five-optional-parameter link builder with no output schema and no annotations, the description conveys the return artifact and its safety property, which covers most of what an agent needs. The remaining gap is the behavior of omitted parameters, which matters because zero parameters are required.

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 examples and enum meanings already documented for all five optional parameters, so the schema does the heavy lifting. The description adds only the framing that these values become pre-selected query components of the URL, which is a modest but real addition over the schema.

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?

States a specific verb and artifact: 'Generate a pre-filled MyLearners 3-step driving school callback URL', then enumerates exactly what gets pre-selected (role, package, transmission, city, suburb). This is clearly distinct from the callback-submission sibling in the sibling list, since the output is a shareable link rather than a booking action.

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?

Usage is only implied: an agent can infer this is for producing a handoff link rather than submitting a request, but the description never says when to prefer it over request_driving_school_callback, nor whether it should be used before or instead of that tool. No exclusions or prerequisites are stated.

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