MyLearners K53 & DMV Practice Test

check_readiness

Calculate statutory South African DLTC triple-hurdle computerized learner's test pass probability across Rules of the Road (min 22/28 or 78.6%), Road Traffic Signs (min 23/28 or 82.1%), and Vehicle Controls (min 6/8 or 75.0%).

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

Input Schema

Name	Required	Description
`rules_score`	No	Rules of the Road score out of 28 questions (statutory pass mark is 22/28)
`signs_score`	No	Road Traffic Signs score out of 28 questions (statutory pass mark is 23/28)
`vehicle_code`	No	Vehicle licence code: 'code_1' (Motorcycle), 'code_2' (Light Motor Vehicle), or 'code_3' (Heavy Motor Vehicle)
`controls_score`	No	Vehicle Controls score out of 8 questions (statutory pass mark is 6/8)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

B3.1/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. It usefully discloses the statutory triple-hurdle logic and per-section minimum marks, which is real behavioral context about how the result is computed. However, it does not say what happens when some scores are omitted (all four parameters are optional), whether the tool is purely computational/read-only, or what form the result takes.

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?

It is a single front-loaded sentence that names the action and the three hurdles without filler. It is dense but every clause carries information, though the repeated pass-mark figures duplicate the schema.

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

Completeness2/5

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

There is no output schema, yet the description never explains what is returned (per-section pass probability, overall verdict, or both). It also leaves unexplained the fact that all four inputs are optional, which is a significant ambiguity for a calculation tool.

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%, and each parameter already documents its scale and statutory pass mark. The description largely repeats those thresholds rather than adding new meaning, so 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 states a specific verb and resource: calculating pass probability for the South African DLTC learner's test across three named sections. It is far clearer than the vague tool name 'check_readiness', but it does not distinguish this tool from siblings like get_outcomes_summary or get_top_mistakes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus the other readiness/stats tools, and no guidance on prerequisites such as needing prior test scores. The agent must infer usage entirely from the name and the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MyLearners K53 & DMV Practice Test tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?