Skip to main content
Glama

request_driving_school_callback

Submit a free South African Code 8 driving school callback lead on behalf of a learner or parent after the user has explicitly confirmed their details in chat. Pure lead enquiry with no online payment required.

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": {
      "booked_by_role": "<booked_by_role>",
      "package_interest": "<package_interest>",
      "transmission": "<transmission>",
      "city": "<city>",
      "suburb": "<suburb>",
      "user_confirmed_submission": "<user_confirmed_submission>"
    },
    "name": "request_driving_school_callback"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity or town for pickup and DLTC testing (e.g., 'Pretoria', 'Centurion', 'Midrand')
nameNoLearner/student full name (required for learner mode; also used as student name if learner_name omitted in parent mode)
emailNoOptional email address for a written package quote
notesNoOptional scheduling or pickup notes such as preferred days, school gate, or target test date (max 300 chars)
phoneNo10-digit South African mobile/WhatsApp number (e.g., '0721234567' or '+27721234567'); required for learner mode
suburbYesExact suburb or area for door-to-door pickup (e.g., 'Waterkloof', 'Montana', 'Irene', 'Waterfall')
payer_nameNoParent or sponsor full name (required when booked_by_role is 'parent')
payer_emailNoOptional parent/sponsor email address for written quote copy
payer_phoneNoParent or sponsor 10-digit South African WhatsApp/mobile number (required when booked_by_role is 'parent')
learner_nameNoChild or student full name (required when booked_by_role is 'parent')
transmissionYesCode 8 vehicle gearbox: 'manual' or 'automatic'
learner_phoneNoOptional 10-digit South African mobile number for the student's lesson pickup coordination
booked_by_roleYesWho is enquiring: 'learner' (for themselves) or 'parent' (parent/sponsor enquiring on behalf of child/student)
package_interestYesSelected package: 'practical_lessons' (R1,900-R5,500 Practical Lessons + Test Car Hire) or 'full_package' (R5,500-R6,500 Full Learner's + Driver's Package)
user_confirmed_submissionYesMust be true ONLY after summarizing all collected details back to the user and receiving their explicit confirmation to submit the callback request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / booked_by_role / description
      Previous value: -"Who is booking: 'learner' (for themselves) or 'parent' (parent/sponsor paying on behalf of child/student)"New value: +"Who is enquiring: 'learner' (for themselves) or 'parent' (parent/sponsor enquiring on behalf of child/student)"
    • removedInput schema / properties / budget_readiness
      Removed value: -{
      -  "description": "How the user plans to pay the school directly: 'ready_full', 'ready_deposit', 'pay_per_lesson', or 'saving_up'",
      -  "enum": [
      -    "ready_full",
      -    "ready_deposit",
      -    "pay_per_lesson",
      -    "saving_up"
      -  ],
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "booked_by_role",
      -  "package_interest",
      -  "transmission",
      -  "city",
      -  "suburb",
      -  "budget_readiness",
      -  "user_confirmed_submission"
      -]New value: +[
      +  "booked_by_role",
      +  "package_interest",
      +  "transmission",
      +  "city",
      +  "suburb",
      +  "user_confirmed_submission"
      +]
  2. Added

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful traits: it is a free lead enquiry, requires no payment, and must only fire after explicit user confirmation. However, it says nothing about what happens after submission — whether a consultant contacts the user, what the success response looks like, or whether duplicate submissions are rejected — which matters for a create-style tool with no output schema.

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 sentences, front-loaded with the action and scope, followed by the confirmation precondition and payment clarification. No redundant restatement of the name or schema fields.

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 15-parameter lead-submission tool with full schema coverage and no output schema, the description covers the essential non-schema facts: free, no payment, and the explicit-confirmation gate. It omits the post-submission outcome and any guidance on sequencing with the options/booking-link siblings, keeping it just short of complete.

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 description coverage is 100%, so the schema already explains role modes, phone formats, and package enums; baseline is 3. The description adds a small amount of meaning by framing the actor as 'learner or parent', pointing at the booked_by_role branching, but it contributes no additional parameter detail beyond that.

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 ('Submit'), resource ('driving school callback lead'), scope ('South African Code 8'), and actor ('on behalf of a learner or parent'). This clearly separates it from siblings such as build_driving_school_booking_link (which produces a link) and get_driving_school_options (which returns choices).

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?

Gives an explicit precondition: only call after the user has explicitly confirmed their details in chat, which matches the user_confirmed_submission gate. It also clarifies the tool is a free lead enquiry with no online payment, but it never names an alternative tool or states when NOT to use it (e.g., when the user hasn't yet chosen a package, use get_driving_school_options first).

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