RegEvidenceHub Taxi

taxi_licence_preflight

Read-onlyIdempotent

Free deterministic decision preflight for ONE supported council/licensing authority on this public AI surface. Use when the user wants applicant, driver, vehicle or fleet readiness, applicable requirements or blockers, missing facts, and next actions before submission or onboarding. Call list_supported_authorities first if coverage or the exact authority name is uncertain. Do not use for multiple-authority comparison; use compare_licensing_requirements instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`payload`	Yes	One-authority applicant/fleet preflight facts. Start by calling list_supported_authorities and use the returned authority name exactly. Additional authority-specific facts are allowed and are evaluated only when the evidence-backed rule bundle declares them.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "taxi_licence_preflightDictOutput",
+  "type": "object"
+}

Changed6 schema fields changedSep 5, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / payload / description

Added value: +"One-authority applicant/fleet preflight facts. Start by calling list_supported_authorities and use the returned authority name exactly. Additional authority-specific facts are allowed and are evaluated only when the evidence-backed rule bundle declares them."

addedInput schema / properties / payload / examples

Added value: +[
+  {
+    "age": 30,
+    "authority": "City of Bradford Metropolitan District Council",
+    "driving_licence_years": 4,
+    "has_pass_plus_certificate": true
+  }
+]

addedInput schema / properties / payload / properties

Added value: +{
+  "age": {
+    "description": "Applicant age in years when relevant to the authority rule being checked.",
+    "minimum": 0,
+    "type": "number"
+  },
+  "authority": {
+    "description": "Exact supported licensing-authority name returned by list_supported_authorities.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "driving_licence_years": {
+    "description": "Completed years the applicant has held the driving licence, when known.",
+    "minimum": 0,
+    "type": "number"
+  },
+  "has_pass_plus_certificate": {
+    "description": "Whether the applicant has a Pass Plus certificate, when relevant.",
+    "type": "boolean"
+  }
+}

addedInput schema / properties / payload / required
```
Added value: +[
+  "authority"
+]
```
removedInput schema / properties / payload / title
```
Removed value: -"Payload"
```

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the deterministic nature, the one-authority constraint, and the need to verify authority coverage via list_supported_authorities. It does not describe error behavior for unsupported authorities, but the annotation coverage lowers the burden.

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?

The description is three sentences, with each sentence carrying distinct value: what the tool does, when to use it, and when to use an alternative. It is front-loaded and free of filler.

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?

Given the nested payload, full schema documentation, output schema, and strong annotations, the description covers purpose, usage, scoping, and routing to sibling tools. Nothing an agent needs to invoke this tool correctly is missing.

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%, so the schema fully documents the payload parameters. The description reinforces the one-authority constraint and the list_supported_authorities prerequisite, which is useful but does not materially extend parameter semantics beyond what the schema already states.

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 the operation ('decision preflight'), scope ('ONE supported council/licensing authority'), and expected outputs (readiness, requirements, blockers, missing facts, next actions). It also distinguishes itself from compare_licensing_requirements by explicitly excluding multiple-authority comparison.

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

Usage Guidelines5/5

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

It states clear use cases ('when the user wants applicant, driver, vehicle or fleet readiness...'), a prerequisite ('Call list_supported_authorities first if coverage or the exact authority name is uncertain'), and an explicit alternative when not to use the tool ('use compare_licensing_requirements instead'). This is comprehensive routing guidance.

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

All RegEvidenceHub Taxi 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?