RegEvidenceHub Taxi

compare_licensing_requirements

Read-onlyIdempotent

Free deterministic comparison for TWO OR MORE supported councils/licensing authorities on this public AI surface. Use when the user wants requirements, blockers or trade-offs compared for the same applicant or fleet, or is choosing where to license. Call list_supported_authorities first if authority names or coverage are uncertain. Do not use for a single-authority readiness check; use taxi_licence_preflight instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`payload`	Yes	Cross-authority comparison request. Call list_supported_authorities first, then supply one or more exact authority names plus the applicant facts to compare. Additional applicant facts are allowed so authority-specific rule inputs are not narrowed.

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": "compare_licensing_requirementsDictOutput",
+  "type": "object"
+}

Changed6 schema fields changedSep 5, 2026

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

addedInput schema / properties / payload / description

Added value: +"Cross-authority comparison request. Call list_supported_authorities first, then supply one or more exact authority names plus the applicant facts to compare. Additional applicant facts are allowed so authority-specific rule inputs are not narrowed."

addedInput schema / properties / payload / examples

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

addedInput schema / properties / payload / properties

Added value: +{
+  "applicant": {
+    "additionalProperties": true,
+    "description": "Applicant/fleet facts applied consistently to every authority in the comparison.",
+    "examples": [
+      {
+        "age": 30,
+        "driving_licence_years": 4,
+        "has_pass_plus_certificate": true
+      }
+    ],
+    "properties": {
+      "age": {
+        "description": "Applicant age in years when relevant to the authority rule being checked.",
+        "minimum": 0,
+        "type": "number"
+      },
+      "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"
+      }
+    },
+    "type": "object"
+  },
+  "authorities": {
+    "description": "Exact supported authority names returned by list_supported_authorities.",
+    "items": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array",
+    "uniqueItems": true
+  }
+}

addedInput schema / properties / payload / required

Added value: +[
+  "authorities",
+  "applicant"
+]

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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds 'Free deterministic comparison' – providing cost and determinism guarantees – and 'public AI surface' context, which is extra behavioral information beyond annotations. No contradiction with annotations.

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?

Four sentences, no filler, front-loaded with the core purpose and scoping. The exclusion and prerequisite are placed early. Every sentence earns its place, making it efficient and easy to parse.

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?

For a comparison tool with a rich input schema and an output schema, the description covers purpose, usage, exclusions, and prerequisites. Nothing essential for correct invocation is missing. The slight 'two or more' vs schema minItems is a minor semantic nuance, not a completeness gap.

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 coverage is 100% (the payload has a detailed description covering the structure and additional facts allowed). The description adds the 'TWO OR MORE' constraint not present in the schema (which allows one authority via minItems:1), providing extra meaning but also creating a slight inconsistency. Since schema does heavy lifting, 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 verb and resource: 'comparison for TWO OR MORE supported councils/licensing authorities'. It clearly distinguishes from siblings by naming the alternative for single-authority checks (taxi_licence_preflight) and the prerequisite (list_supported_authorities). This leaves no ambiguity about what the tool does.

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?

Explicit when-to-use guidance: 'when the user wants requirements, blockers or trade-offs compared for the same applicant or fleet, or is choosing where to license'. Also explicit when-not-to-use: 'Do not use for a single-authority readiness check' with a named alternative, and instructs to call list_supported_authorities first if uncertain. This is exemplary usage routing.

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?