RegEvidenceHub Taxi

taxi_licence_preflight

Read-onlyIdempotent

Run a payment-free deterministic one-authority licensing preflight.

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.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds valuable non-obvious traits—'payment-free' and 'deterministic'—that are not present in the annotations. It does not detail auth or rate limits, but the annotation coverage lowers that 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 a single 7-word sentence with no filler. It front-loads the action and the most decision-relevant qualifiers: payment-free, deterministic, one-authority.

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 preflight tool with rich annotations, a full output schema, and a well-documented input schema, the description covers the essential decision factors. It is slightly light on explicit sibling differentiation, but the 'one-authority' scope and schema's list_supported_authorities hint make it adequately complete.

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 the payload's nested schema already provides detailed parameter semantics, including the requirement to use exact authority names and allow additional facts. The tool description itself adds no parameter-level meaning, so baseline 3 is appropriate.

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 states a specific action ('Run'), a specific resource ('licensing preflight'), and clear scope constraints ('one-authority', 'payment-free', 'deterministic'). This makes it easy to distinguish from sibling tools like compare_licensing_requirements, list_supported_authorities, and taxi_phv_info.

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 context is only implied: 'one-authority' suggests it is not for comparing licensing requirements, and the schema says to start by calling list_supported_authorities. However, the description itself gives no explicit when-to-use or when-not-to-use guidance and does not name any alternative tools.

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?