Skip to main content
Glama

RegEvidenceHub Premises

by io.github.ChanghuLiu
OverviewDiscussionsAdmin

Server Details

RegEvidenceHub Premises: UK premises-licensing preflight for supported authorities.

Ownership verified
Status
Healthy
Uptime
99.8% over 21 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: checking a single authority's support, listing all supported authorities, explaining the plugin scope, and describing preflight input categories. Even though authority_support_check and list_supported_authorities are related, their single-item vs. list behavior is unambiguous.

Naming Consistency4/5

All tool names are lowercase snake_case and readable, but they do not follow one consistent pattern: two are verb-led (list_supported_authorities, authority_support_check uses check as a noun) while the other two are noun phrases. The naming is still predictable and professional overall, with only minor style deviations.

Tool Count5/5

Four tools is well-scoped for a read-only premises-licensing navigator. Each tool provides a distinct piece of informational or preflight-preparation value without unnecessary overlap or bloat.

Completeness4/5

The tool set covers the main read-only workflows: checking supported authorities, listing them, understanding the plugin scope, and preparing preflight facts. There are minor omissions such as per-authority detail or decision-checking functionality, but those appear intentionally outside the stated read-only scope.

Available Tools

4 tools
authority_support_checkA
Read-onlyIdempotent
Inspect

Check whether one named local licensing authority is supported. Does not make a licensing decision.

ParametersJSON Schema
NameRequiredDescriptionDefault
authorityYes

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond these: it explicitly states that this tool does not make a licensing decision, preventing agents from over-interpreting the result. This is valuable negative disclosure even though the description does not address edge cases like unknown authority names.

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 short sentences with no filler. The first sentence states the core action and object, and the second sentence adds an important boundary that prevents misuse. Every word earns its place.

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 tool with one required string parameter, an output schema, and strong safety annotations, the description is nearly complete. It explains the input, the scope, and a critical non-behavior. It does not mention how to obtain valid authority names, but the sibling tool list_supported_authorities implies that route and the output schema can describe return values.

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 coverage is 0%, so the description carries the burden of explaining the single 'authority' parameter. It does so by identifying it as a named local licensing authority, which clarifies that the string is a display name or identifier for a licensing authority rather than an arbitrary value. It could be more explicit about the expected format or source, but it adds enough meaning for such a simple parameter.

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 uses a specific verb, 'check whether...is supported', and clearly names the resource: one named local licensing authority. It also distinguishes itself from sibling list_supported_authorities by emphasizing the single-authority scope. The added clarification that it does not make a licensing decision removes ambiguity about its role.

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?

The description clearly implies when to use it: when you need to verify support for a single named authority rather than listing all supported authorities. It does not explicitly name alternatives or state when not to use it, but the single-authority framing provides enough contextual guidance for an agent to select it appropriately.

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

list_supported_authoritiesA
Read-onlyIdempotent
Inspect

List local licensing authorities currently supported by the premises-licensing decision service.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds minimal context with 'currently supported,' implying the set may change over time, but it does not disclose return behavior or other traits beyond what annotations already provide.

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?

A single, well-formed sentence that immediately states the action and the resource. There is no filler, and the key qualifier 'currently supported' is included without unnecessary elaboration.

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 parameterless read-only listing tool with an output schema present and safety covered by annotations, the description is fully sufficient. Nothing an agent needs to select or 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is nothing for the description to explain. The rubric sets a baseline of 4 for parameterless tools, and the description appropriately spends no space on parameters.

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 a specific verb ('List') and resource ('local licensing authorities currently supported by the premises-licensing decision service'). This clearly differentiates it from sibling tools like authority_support_check, which likely checks a single authority rather than enumerating all supported ones.

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?

The intended use is implied by the clear verb and resource: an agent would call this when it needs to know which authorities are supported. However, it does not explicitly mention when to prefer this over siblings or provide exclusion criteria, so the guidance is inferred rather than stated.

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

premises_plugin_infoA
Read-onlyIdempotent
Inspect

Explain the read-only UK Premises Licence Navigator scope.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds the UK Premises Licence Navigator scope context but no further behavioral detail, so it is adequate without adding much beyond the annotation coverage.

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, front-loaded sentence with no filler. Every word contributes to the purpose and safety profile.

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 no-argument informational tool with an output schema and complete annotations, the description covers the essential context. A little more specificity about what the returned 'scope' explanation contains would make it fully 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?

The input schema has zero parameters, so parameter semantics are not a burden on the description. The baseline of 4 applies; the description does not need to explain parameters that do not exist.

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 clear verb ('Explain') and a distinct resource ('read-only UK Premises Licence Navigator scope'), making the tool's informational purpose evident. It is distinguishable from sibling tools, though it does not explicitly name them or contrast itself.

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?

The wording implies the tool is for obtaining an overview of the plugin's scope and that it is read-only, but it does not specify when to prefer this over authority_support_check, list_supported_authorities, or premises_preflight_input_guide.

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

premises_preflight_input_guideA
Read-onlyIdempotent
Inspect

Show the categories of facts to prepare before a premises-licensing preflight. Use only user-supplied facts; never infer or default missing authority, venue, activity, alcohol, hours, or exemption facts.

ParametersJSON Schema
NameRequiredDescriptionDefault
activityNo

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, and the description adds behavioral context beyond those: it explicitly warns against inferring or defaulting facts, which aligns with openWorldHint=false. This gives agents a clear operational constraint not present in the structured 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?

Two sentences with zero waste. The main purpose is front-loaded, and the second sentence adds an essential constraint. Every word earns its place.

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

Completeness3/5

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

The description covers the core purpose and a key behavioral rule, and the output schema covers return values. However, it leaves the 'activity' parameter entirely unexplained, and it does not situate itself relative to the sibling tools. Adequate but with a clear gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the 'activity' parameter. It does not mention the parameter at all, leaving its meaning and impact on the guide unexplained. With a single optional parameter, this is a notable gap.

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: 'Show the categories of facts to prepare before a premises-licensing preflight.' This clearly distinguishes the tool from its siblings, which focus on authority checks and plugin info. The purpose is unambiguous and instantly actionable.

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?

The description provides clear context (before a premises-licensing preflight) and a crucial rule: 'Use only user-supplied facts; never infer or default missing authority, venue, activity, alcohol, hours, or exemption facts.' It does not explicitly name alternatives or exclusions relative to siblings, but the usage is well implied.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 10 tool updates
    • Addedauthority_support_check
    • Removedcompare_licensing_requirements
    • Removedlicensing_source_status
    • Removedlocal_policy_capabilities
    • Removedpreflight_readiness
    • Removedpremises_licence_info
    • Removedpremises_licence_preflight
    • Addedpremises_plugin_info
    • Addedpremises_preflight_input_guide
    • Removedsource_fingerprint_status
  2. 2 tool updates
    • Changedcompare_licensing_requirements45 fields changed
      • changedInput schema / properties / birmingham_application_type / description
        Previous value: -"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."New value: +"Birmingham application type: new, full variation, minor variation, other, or unknown."
      • changedInput schema / properties / birmingham_primary_alcohol_business / description
        Previous value: -"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Birmingham business is primarily an alcohol-led premises, when known for the encoded fee/process branch."
      • changedInput schema / properties / birmingham_rateable_value_gbp / description
        Previous value: -"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."New value: +"Birmingham premises rateable value in whole GBP, when known; used for the encoded fee/process branch."
      • changedInput schema / properties / birmingham_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Birmingham application."
      • changedInput schema / properties / brighton_delivery_only_after_midnight / description
        Previous value: -"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Brighton and Hove operation is delivery-only after midnight."
      • changedInput schema / properties / brighton_good_operator_holder_at_application_and_determination / description
        Previous value: -"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the applicant held the Brighton and Hove good-operator status at both application and determination, when known."
      • changedInput schema / properties / brighton_good_operator_no_formal_intervention_3_to_5_years / description
        Previous value: -"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Brighton and Hove operator had no formal intervention in the relevant three-to-five-year lookback period, when known."
      • changedInput schema / properties / brighton_is_variation_application / description
        Previous value: -"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Brighton and Hove application is a variation rather than a new application."
      • changedInput schema / properties / brighton_requested_end_time / description
        Previous value: -"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."New value: +"Requested closing time in Brighton and Hove local time, formatted HH:MM, when the local timing matrix applies."
      • changedInput schema / properties / bristol_application_type / description
        Previous value: -"Authority-specific scenario fact for Bristol; provide only when known and relevant to that authority's encoded local policy."New value: +"Bristol application type: new, material variation, other, or unknown."
      • changedInput schema / properties / bristol_in_cumulative_impact_area / description
        Previous value: -"Authority-specific scenario fact for Bristol; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Bristol premises is in a supported cumulative-impact area."
      • changedInput schema / properties / bristol_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Bristol; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Bristol application."
      • changedInput schema / properties / camden_cumulative_impact_risk / description
        Previous value: -"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Camden scenario has a cumulative-impact risk signal requiring policy review."
      • changedInput schema / properties / camden_day_type / description
        Previous value: -"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."New value: +"Camden day category: Monday-Thursday, Friday-Saturday, or Sunday."
      • changedInput schema / properties / camden_framework_category / description
        Previous value: -"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."New value: +"Camden framework category: alcohol on-premises only, alcohol off-premises authorised, no alcohol, or unknown."
      • changedInput schema / properties / camden_outside_framework_hours / description
        Previous value: -"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Camden proposal is outside the encoded framework hours."
      • changedInput schema / properties / camden_requested_end_time / description
        Previous value: -"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."New value: +"Requested Camden closing/end time in local HH:MM format."
      • changedInput schema / properties / camden_requested_start_time / description
        Previous value: -"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."New value: +"Requested Camden opening/start time in local HH:MM format."
      • changedInput schema / properties / cardiff_application_type / description
        Previous value: -"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."New value: +"Cardiff application type: grant, full variation, minor variation, other, or unknown."
      • changedInput schema / properties / cardiff_in_cumulative_impact_area / description
        Previous value: -"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Cardiff premises is in a supported cumulative-impact area."
      • changedInput schema / properties / cardiff_ndrv_status / description
        Previous value: -"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Cardiff premises rateable-value status is known, has no NDRV, is under construction/unassessed, or remains unknown."
      • changedInput schema / properties / cardiff_primary_alcohol_business / description
        Previous value: -"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Cardiff business is primarily an alcohol-led premises, when known for the encoded fee/process branch."
      • changedInput schema / properties / cardiff_rateable_value_gbp / description
        Previous value: -"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."New value: +"Cardiff premises rateable value in whole GBP, when known; used for the encoded fee/process branch."
      • changedInput schema / properties / cardiff_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Cardiff application."
      • changedInput schema / properties / hot_food_end_hour / description
        Previous value: -"End hour, 0-23 local time, for hot food or hot drink supply when relevant."New value: +"End hour, 0-24 local time, for hot food or hot drink supply when relevant."
      • changedInput schema / properties / leeds_application_type / description
        Previous value: -"Authority-specific scenario fact for Leeds; provide only when known and relevant to that authority's encoded local policy."New value: +"Leeds application type: new, variation, other, or unknown."
      • changedInput schema / properties / leeds_cumulative_area / description
        Previous value: -"Authority-specific scenario fact for Leeds; provide only when known and relevant to that authority's encoded local policy."New value: +"Leeds cumulative-impact area classification, such as city centre, Headingley, Hyde Park, or another supported area."
      • changedInput schema / properties / leeds_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Leeds; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Leeds application."
      • changedInput schema / properties / liverpool_application_type / description
        Previous value: -"Authority-specific scenario fact for Liverpool; provide only when known and relevant to that authority's encoded local policy."New value: +"Liverpool application type: new, full variation, minor variation, or another/unknown type."
      • changedInput schema / properties / liverpool_minor_variation_extends_alcohol_hours_23_07 / description
        Previous value: -"Authority-specific scenario fact for Liverpool; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether a Liverpool minor variation would extend alcohol hours into the 23:00-07:00 period."
      • changedInput schema / properties / liverpool_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Liverpool; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Liverpool application."
      • changedInput schema / properties / manchester_delivery_only / description
        Previous value: -"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Manchester operation is delivery-only."
      • changedInput schema / properties / manchester_operating_phase / description
        Previous value: -"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."New value: +"Manchester operating phase: twilight/evening, night-time, late-night, or unknown."
      • changedInput schema / properties / manchester_policy_area / description
        Previous value: -"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."New value: +"Manchester policy-area classification: Fallowfield special-policy area, Withington special-policy area, other, or unknown."
      • changedInput schema / properties / manchester_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Manchester application."
      • changedInput schema / properties / newcastle_application_type / description
        Previous value: -"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."New value: +"Newcastle application type: new, full variation, minor variation, other, or unknown."
      • changedInput schema / properties / newcastle_outside_framework_hours / description
        Previous value: -"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Newcastle proposal is outside the applicable framework hours."
      • changedInput schema / properties / newcastle_policy_area / description
        Previous value: -"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."New value: +"Newcastle policy-area classification: cumulative-impact area, special-stress area, other, or unknown."
      • changedInput schema / properties / newcastle_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Newcastle application."
      • changedInput schema / properties / westminster_day_type / description
        Previous value: -"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."New value: +"Westminster day category: Monday-Thursday, Friday-Saturday, Sunday, or Sunday before a bank holiday."
      • changedInput schema / properties / westminster_in_west_end_ciz / description
        Previous value: -"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Westminster premises is in the West End cumulative-impact zone."
      • changedInput schema / properties / westminster_outside_core_hours / description
        Previous value: -"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Westminster proposal is outside the encoded core hours."
      • changedInput schema / properties / westminster_premises_use / description
        Previous value: -"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."New value: +"Westminster premises-use category used by the core-hours policy matrix."
      • changedInput schema / properties / westminster_requested_end_time / description
        Previous value: -"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."New value: +"Requested Westminster closing/end time in local HH:MM format."
      • changedInput schema / properties / westminster_requested_start_time / description
        Previous value: -"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."New value: +"Requested Westminster opening/start time in local HH:MM format."
    • Changedpremises_licence_preflight45 fields changed
      • changedInput schema / properties / birmingham_application_type / description
        Previous value: -"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."New value: +"Birmingham application type: new, full variation, minor variation, other, or unknown."
      • changedInput schema / properties / birmingham_primary_alcohol_business / description
        Previous value: -"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Birmingham business is primarily an alcohol-led premises, when known for the encoded fee/process branch."
      • changedInput schema / properties / birmingham_rateable_value_gbp / description
        Previous value: -"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."New value: +"Birmingham premises rateable value in whole GBP, when known; used for the encoded fee/process branch."
      • changedInput schema / properties / birmingham_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Birmingham application."
      • changedInput schema / properties / brighton_delivery_only_after_midnight / description
        Previous value: -"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Brighton and Hove operation is delivery-only after midnight."
      • changedInput schema / properties / brighton_good_operator_holder_at_application_and_determination / description
        Previous value: -"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the applicant held the Brighton and Hove good-operator status at both application and determination, when known."
      • changedInput schema / properties / brighton_good_operator_no_formal_intervention_3_to_5_years / description
        Previous value: -"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Brighton and Hove operator had no formal intervention in the relevant three-to-five-year lookback period, when known."
      • changedInput schema / properties / brighton_is_variation_application / description
        Previous value: -"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Brighton and Hove application is a variation rather than a new application."
      • changedInput schema / properties / brighton_requested_end_time / description
        Previous value: -"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."New value: +"Requested closing time in Brighton and Hove local time, formatted HH:MM, when the local timing matrix applies."
      • changedInput schema / properties / bristol_application_type / description
        Previous value: -"Authority-specific scenario fact for Bristol; provide only when known and relevant to that authority's encoded local policy."New value: +"Bristol application type: new, material variation, other, or unknown."
      • changedInput schema / properties / bristol_in_cumulative_impact_area / description
        Previous value: -"Authority-specific scenario fact for Bristol; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Bristol premises is in a supported cumulative-impact area."
      • changedInput schema / properties / bristol_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Bristol; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Bristol application."
      • changedInput schema / properties / camden_cumulative_impact_risk / description
        Previous value: -"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Camden scenario has a cumulative-impact risk signal requiring policy review."
      • changedInput schema / properties / camden_day_type / description
        Previous value: -"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."New value: +"Camden day category: Monday-Thursday, Friday-Saturday, or Sunday."
      • changedInput schema / properties / camden_framework_category / description
        Previous value: -"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."New value: +"Camden framework category: alcohol on-premises only, alcohol off-premises authorised, no alcohol, or unknown."
      • changedInput schema / properties / camden_outside_framework_hours / description
        Previous value: -"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Camden proposal is outside the encoded framework hours."
      • changedInput schema / properties / camden_requested_end_time / description
        Previous value: -"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."New value: +"Requested Camden closing/end time in local HH:MM format."
      • changedInput schema / properties / camden_requested_start_time / description
        Previous value: -"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."New value: +"Requested Camden opening/start time in local HH:MM format."
      • changedInput schema / properties / cardiff_application_type / description
        Previous value: -"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."New value: +"Cardiff application type: grant, full variation, minor variation, other, or unknown."
      • changedInput schema / properties / cardiff_in_cumulative_impact_area / description
        Previous value: -"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Cardiff premises is in a supported cumulative-impact area."
      • changedInput schema / properties / cardiff_ndrv_status / description
        Previous value: -"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Cardiff premises rateable-value status is known, has no NDRV, is under construction/unassessed, or remains unknown."
      • changedInput schema / properties / cardiff_primary_alcohol_business / description
        Previous value: -"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Cardiff business is primarily an alcohol-led premises, when known for the encoded fee/process branch."
      • changedInput schema / properties / cardiff_rateable_value_gbp / description
        Previous value: -"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."New value: +"Cardiff premises rateable value in whole GBP, when known; used for the encoded fee/process branch."
      • changedInput schema / properties / cardiff_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Cardiff application."
      • changedInput schema / properties / hot_food_end_hour / description
        Previous value: -"End hour, 0-23 local time, for hot food or hot drink supply when relevant."New value: +"End hour, 0-24 local time, for hot food or hot drink supply when relevant."
      • changedInput schema / properties / leeds_application_type / description
        Previous value: -"Authority-specific scenario fact for Leeds; provide only when known and relevant to that authority's encoded local policy."New value: +"Leeds application type: new, variation, other, or unknown."
      • changedInput schema / properties / leeds_cumulative_area / description
        Previous value: -"Authority-specific scenario fact for Leeds; provide only when known and relevant to that authority's encoded local policy."New value: +"Leeds cumulative-impact area classification, such as city centre, Headingley, Hyde Park, or another supported area."
      • changedInput schema / properties / leeds_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Leeds; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Leeds application."
      • changedInput schema / properties / liverpool_application_type / description
        Previous value: -"Authority-specific scenario fact for Liverpool; provide only when known and relevant to that authority's encoded local policy."New value: +"Liverpool application type: new, full variation, minor variation, or another/unknown type."
      • changedInput schema / properties / liverpool_minor_variation_extends_alcohol_hours_23_07 / description
        Previous value: -"Authority-specific scenario fact for Liverpool; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether a Liverpool minor variation would extend alcohol hours into the 23:00-07:00 period."
      • changedInput schema / properties / liverpool_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Liverpool; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Liverpool application."
      • changedInput schema / properties / manchester_delivery_only / description
        Previous value: -"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Manchester operation is delivery-only."
      • changedInput schema / properties / manchester_operating_phase / description
        Previous value: -"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."New value: +"Manchester operating phase: twilight/evening, night-time, late-night, or unknown."
      • changedInput schema / properties / manchester_policy_area / description
        Previous value: -"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."New value: +"Manchester policy-area classification: Fallowfield special-policy area, Withington special-policy area, other, or unknown."
      • changedInput schema / properties / manchester_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Manchester application."
      • changedInput schema / properties / newcastle_application_type / description
        Previous value: -"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."New value: +"Newcastle application type: new, full variation, minor variation, other, or unknown."
      • changedInput schema / properties / newcastle_outside_framework_hours / description
        Previous value: -"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Newcastle proposal is outside the applicable framework hours."
      • changedInput schema / properties / newcastle_policy_area / description
        Previous value: -"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."New value: +"Newcastle policy-area classification: cumulative-impact area, special-stress area, other, or unknown."
      • changedInput schema / properties / newcastle_relevant_representations / description
        Previous value: -"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether relevant representations have been made for the Newcastle application."
      • changedInput schema / properties / westminster_day_type / description
        Previous value: -"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."New value: +"Westminster day category: Monday-Thursday, Friday-Saturday, Sunday, or Sunday before a bank holiday."
      • changedInput schema / properties / westminster_in_west_end_ciz / description
        Previous value: -"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Westminster premises is in the West End cumulative-impact zone."
      • changedInput schema / properties / westminster_outside_core_hours / description
        Previous value: -"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."New value: +"Whether the Westminster proposal is outside the encoded core hours."
      • changedInput schema / properties / westminster_premises_use / description
        Previous value: -"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."New value: +"Westminster premises-use category used by the core-hours policy matrix."
      • changedInput schema / properties / westminster_requested_end_time / description
        Previous value: -"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."New value: +"Requested Westminster closing/end time in local HH:MM format."
      • changedInput schema / properties / westminster_requested_start_time / description
        Previous value: -"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."New value: +"Requested Westminster opening/start time in local HH:MM format."
  3. 6 tool updates
    • Changedcompare_licensing_requirements57 fields changed
      • addedInput schema / properties / applicant_age / description
        Added value: +"Applicant age in completed years; used for deterministic age-related Licensing Act checks."
      • addedInput schema / properties / authorities / description
        Added value: +"Two or more supported local licensing authorities to compare using the same premises facts."
      • addedInput schema / properties / birmingham_application_type / description
        Added value: +"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / birmingham_primary_alcohol_business / description
        Added value: +"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / birmingham_rateable_value_gbp / description
        Added value: +"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / birmingham_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / brighton_delivery_only_after_midnight / description
        Added value: +"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / brighton_good_operator_holder_at_application_and_determination / description
        Added value: +"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / brighton_good_operator_no_formal_intervention_3_to_5_years / description
        Added value: +"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / brighton_is_variation_application / description
        Added value: +"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / brighton_requested_end_time / description
        Added value: +"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / bristol_application_type / description
        Added value: +"Authority-specific scenario fact for Bristol; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / bristol_in_cumulative_impact_area / description
        Added value: +"Authority-specific scenario fact for Bristol; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / bristol_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Bristol; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / camden_cumulative_impact_risk / description
        Added value: +"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / camden_day_type / description
        Added value: +"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / camden_framework_category / description
        Added value: +"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / camden_outside_framework_hours / description
        Added value: +"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / camden_requested_end_time / description
        Added value: +"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / camden_requested_start_time / description
        Added value: +"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / cardiff_application_type / description
        Added value: +"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / cardiff_in_cumulative_impact_area / description
        Added value: +"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / cardiff_ndrv_status / description
        Added value: +"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / cardiff_primary_alcohol_business / description
        Added value: +"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / cardiff_rateable_value_gbp / description
        Added value: +"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / cardiff_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / dps_has_personal_licence / description
        Added value: +"Whether the proposed designated premises supervisor holds the required personal licence, if known."
      • addedInput schema / properties / entertainment_exempt / description
        Added value: +"Whether a known statutory exemption applies to the proposed entertainment."
      • addedInput schema / properties / hot_food_end_hour / description
        Added value: +"End hour, 0-23 local time, for hot food or hot drink supply when relevant."
      • addedInput schema / properties / hot_food_start_hour / description
        Added value: +"Start hour, 0-23 local time, for hot food or hot drink supply when relevant."
      • addedInput schema / properties / leeds_application_type / description
        Added value: +"Authority-specific scenario fact for Leeds; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / leeds_cumulative_area / description
        Added value: +"Authority-specific scenario fact for Leeds; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / leeds_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Leeds; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / liverpool_application_type / description
        Added value: +"Authority-specific scenario fact for Liverpool; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / liverpool_minor_variation_extends_alcohol_hours_23_07 / description
        Added value: +"Authority-specific scenario fact for Liverpool; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / liverpool_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Liverpool; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / manchester_delivery_only / description
        Added value: +"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / manchester_operating_phase / description
        Added value: +"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / manchester_policy_area / description
        Added value: +"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / manchester_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / members_club / description
        Added value: +"Whether the premises is operating as a qualifying members club rather than ordinary public premises."
      • addedInput schema / properties / newcastle_application_type / description
        Added value: +"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / newcastle_outside_framework_hours / description
        Added value: +"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / newcastle_policy_area / description
        Added value: +"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / newcastle_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / premises_zone / description
        Added value: +"Known local premises/policy zone classification when relevant to the selected authority."
      • addedInput schema / properties / regulated_entertainment / description
        Added value: +"Whether the proposed operation includes regulated entertainment."
      • addedInput schema / properties / sells_alcohol / description
        Added value: +"Whether the proposed premises will sell or supply alcohol."
      • addedInput schema / properties / supplies_hot_food_or_drink / description
        Added value: +"Whether hot food or hot drink will be supplied as part of the proposed operation."
      • addedInput schema / properties / venue_type / description
        Added value: +"Type of venue or premises use when known and relevant to the selected authority."
      • addedInput schema / properties / westminster_day_type / description
        Added value: +"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / westminster_in_west_end_ciz / description
        Added value: +"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / westminster_outside_core_hours / description
        Added value: +"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / westminster_premises_use / description
        Added value: +"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / westminster_requested_end_time / description
        Added value: +"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / westminster_requested_start_time / description
        Added value: +"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Evidence-linked comparison of the same premises facts across supported authorities.",
+  "properties": {
+    "comparison_note": {
+      "description": "Scope and evidence-boundary note for the comparison.",
+      "type": "string"
+    },
+    "results": {
+      "description": "One deterministic preflight result per requested authority.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
    • Changedlicensing_source_status1 field changed
      • addedInput schema / properties / authority / description
        Added value: +"Supported local licensing authority name or slug for the premises being assessed."
    • Changedlocal_policy_capabilities2 fields changed
      • addedInput schema / properties / authority / description
        Added value: +"Supported local licensing authority name or slug for the premises being assessed."
      • addedInput schema / properties / provided_facts / description
        Added value: +"Facts already collected for the authority-specific scenario; used only to identify missing inputs/readiness."
    • Changedpreflight_readiness2 fields changed
      • addedInput schema / properties / authority / description
        Added value: +"Supported local licensing authority name or slug for the premises being assessed."
      • addedInput schema / properties / provided_facts / description
        Added value: +"Facts already collected for the authority-specific scenario; used only to identify missing inputs/readiness."
    • Changedpremises_licence_preflight57 fields changed
      • addedInput schema / properties / applicant_age / description
        Added value: +"Applicant age in completed years; used for deterministic age-related Licensing Act checks."
      • addedInput schema / properties / authority / description
        Added value: +"Supported local licensing authority name or slug for the premises being assessed."
      • addedInput schema / properties / birmingham_application_type / description
        Added value: +"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / birmingham_primary_alcohol_business / description
        Added value: +"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / birmingham_rateable_value_gbp / description
        Added value: +"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / birmingham_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Birmingham; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / brighton_delivery_only_after_midnight / description
        Added value: +"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / brighton_good_operator_holder_at_application_and_determination / description
        Added value: +"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / brighton_good_operator_no_formal_intervention_3_to_5_years / description
        Added value: +"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / brighton_is_variation_application / description
        Added value: +"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / brighton_requested_end_time / description
        Added value: +"Authority-specific scenario fact for Brighton; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / bristol_application_type / description
        Added value: +"Authority-specific scenario fact for Bristol; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / bristol_in_cumulative_impact_area / description
        Added value: +"Authority-specific scenario fact for Bristol; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / bristol_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Bristol; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / camden_cumulative_impact_risk / description
        Added value: +"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / camden_day_type / description
        Added value: +"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / camden_framework_category / description
        Added value: +"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / camden_outside_framework_hours / description
        Added value: +"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / camden_requested_end_time / description
        Added value: +"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / camden_requested_start_time / description
        Added value: +"Authority-specific scenario fact for Camden; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / cardiff_application_type / description
        Added value: +"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / cardiff_in_cumulative_impact_area / description
        Added value: +"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / cardiff_ndrv_status / description
        Added value: +"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / cardiff_primary_alcohol_business / description
        Added value: +"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / cardiff_rateable_value_gbp / description
        Added value: +"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / cardiff_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Cardiff; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / dps_has_personal_licence / description
        Added value: +"Whether the proposed designated premises supervisor holds the required personal licence, if known."
      • addedInput schema / properties / entertainment_exempt / description
        Added value: +"Whether a known statutory exemption applies to the proposed entertainment."
      • addedInput schema / properties / hot_food_end_hour / description
        Added value: +"End hour, 0-23 local time, for hot food or hot drink supply when relevant."
      • addedInput schema / properties / hot_food_start_hour / description
        Added value: +"Start hour, 0-23 local time, for hot food or hot drink supply when relevant."
      • addedInput schema / properties / leeds_application_type / description
        Added value: +"Authority-specific scenario fact for Leeds; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / leeds_cumulative_area / description
        Added value: +"Authority-specific scenario fact for Leeds; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / leeds_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Leeds; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / liverpool_application_type / description
        Added value: +"Authority-specific scenario fact for Liverpool; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / liverpool_minor_variation_extends_alcohol_hours_23_07 / description
        Added value: +"Authority-specific scenario fact for Liverpool; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / liverpool_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Liverpool; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / manchester_delivery_only / description
        Added value: +"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / manchester_operating_phase / description
        Added value: +"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / manchester_policy_area / description
        Added value: +"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / manchester_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Manchester; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / members_club / description
        Added value: +"Whether the premises is operating as a qualifying members club rather than ordinary public premises."
      • addedInput schema / properties / newcastle_application_type / description
        Added value: +"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / newcastle_outside_framework_hours / description
        Added value: +"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / newcastle_policy_area / description
        Added value: +"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / newcastle_relevant_representations / description
        Added value: +"Authority-specific scenario fact for Newcastle; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / premises_zone / description
        Added value: +"Known local premises/policy zone classification when relevant to the selected authority."
      • addedInput schema / properties / regulated_entertainment / description
        Added value: +"Whether the proposed operation includes regulated entertainment."
      • addedInput schema / properties / sells_alcohol / description
        Added value: +"Whether the proposed premises will sell or supply alcohol."
      • addedInput schema / properties / supplies_hot_food_or_drink / description
        Added value: +"Whether hot food or hot drink will be supplied as part of the proposed operation."
      • addedInput schema / properties / venue_type / description
        Added value: +"Type of venue or premises use when known and relevant to the selected authority."
      • addedInput schema / properties / westminster_day_type / description
        Added value: +"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / westminster_in_west_end_ciz / description
        Added value: +"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / westminster_outside_core_hours / description
        Added value: +"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / westminster_premises_use / description
        Added value: +"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / westminster_requested_end_time / description
        Added value: +"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."
      • addedInput schema / properties / westminster_requested_start_time / description
        Added value: +"Authority-specific scenario fact for Westminster; provide only when known and relevant to that authority's encoded local policy."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Deterministic evidence-linked premises-licence preflight result.",
+  "properties": {
+    "authority": {
+      "description": "Authority evaluated.",
+      "type": "string"
+    },
+    "blocking_requirements": {
+      "description": "Blocking or mandatory requirements identified.",
+      "items": {},
+      "type": "array"
+    },
+    "local_policy": {
+      "additionalProperties": true,
+      "description": "Authority-specific evidence and local-policy status.",
+      "type": "object"
+    },
+    "missing_inputs": {
+      "description": "Facts still required for a stronger conclusion.",
+      "items": {},
+      "type": "array"
+    },
+    "next_actions": {
+      "description": "Recommended next actions before submission.",
+      "items": {},
+      "type": "array"
+    },
+    "status": {
+      "description": "Decision/readiness status. Unresolved evidence or facts may fail closed.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • Changedsource_fingerprint_status1 field changed
      • addedInput schema / properties / authority / description
        Added value: +"Supported local licensing authority name or slug for the premises being assessed."
  4. 8 tool updates
    • First observedcompare_licensing_requirements
    • First observedlicensing_source_status
    • First observedlist_supported_authorities
    • First observedlocal_policy_capabilities
    • First observedpreflight_readiness
    • First observedpremises_licence_info
    • First observedpremises_licence_preflight
    • First observedsource_fingerprint_status

Publisher details

Operator
RegEvidenceHub · Publisher source
Operator website
https://www.regevidencehub.com · Publisher source
Vendor relationship
Independent
Documentation
https://premises.regevidencehub.com · Publisher source
Trust center
Not available
Restrictions
Free discovery, readiness, authority coverage, and source-status tools require no authentication. Decision tools such as premises licence preflight and multi-authority comparison may require x402 payment. Coverage is limited to supported UK licensing authorities and official-source evidence available to the service. · Publisher source

Related MCP Connectors

Related MCP Servers

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