Skip to main content
Glama
Sign In

HouseFile UK property licensing checker

by app.housefile
OverviewDiscussionsAdmin

Upcoming licensing changes

upcoming_licensing_changes
Read-onlyIdempotent

What’s coming: schemes proposed or starting soon, and recent changes to schemes in HouseFile’s records (started, ended, fee, dates or area changed), newest first. Optionally for one council, and for a number of months ahead and back (6 by default, at most 24). For all councils the lists stop at the 15 soonest schemes and the 10 latest changes, with the totals; ask for one council to see all of its own.

Input Schema

NameRequiredDescriptionDefault
councilNoA council name, part of one, or its GSS code
within_monthsNoMonths ahead and back to look, 6 by default

Output Schema

NameRequiredDescriptionDefault
noteYesWhat the stages mean, and how to see more when a list was cut short
resultYes
councilYes
upcomingYesSoonest first, then proposals with no start date by council; at most 15 when no council is given
candidatesYes
disclaimerYes
within_monthsYes
recent_changesYesNewest first, at most 10 when no council is given
upcoming_totalYesHow many schemes are proposed or starting soon; more than listed when the list was cut short
recent_changes_totalYesHow many changes there were in the window; more than listed when the list was cut short

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedOutput schema / properties / note
      Added value: +{
+  "description": "What the stages mean, and how to see more when a list was cut short",
+  "type": "string"
+}
    • addedOutput schema / properties / recent_changes / description
      Added value: +"Newest first, at most 10 when no council is given"
    • addedOutput schema / properties / recent_changes_total
      Added value: +{
+  "description": "How many changes there were in the window; more than listed when the list was cut short",
+  "type": "number"
+}
    • addedOutput schema / properties / upcoming / description
      Added value: +"Soonest first, then proposals with no start date by council; at most 15 when no council is given"
    • removedOutput schema / properties / upcoming / items / properties / applicability
      Removed value: -{
-  "anyOf": [
-    {
-      "enum": [
-        "applies",
-        "conditional",
-        "boundary_uncertain",
-        "does_not_apply",
-        "not_covered"
-      ],
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Whether the postcode falls in the scheme’s area on our records, as for a scheme in force. Null where no postcode was given"
-}
    • removedOutput schema / properties / upcoming / items / properties / note
      Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • removedOutput schema / properties / upcoming / items / properties / summary
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / upcoming / items / required
      Previous value: -[
-  "scheme_name",
-  "scheme_type",
-  "council",
-  "stage",
-  "applicability",
-  "note",
-  "expected_start_date",
-  "end_date",
-  "summary",
-  "source_url",
-  "last_verified_at",
-  "housefile_url"
-]New value: +[
+  "scheme_name",
+  "scheme_type",
+  "council",
+  "stage",
+  "expected_start_date",
+  "end_date",
+  "source_url",
+  "last_verified_at",
+  "housefile_url"
+]
    • addedOutput schema / properties / upcoming_total
      Added value: +{
+  "description": "How many schemes are proposed or starting soon; more than listed when the list was cut short",
+  "type": "number"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result",
-  "council",
-  "within_months",
-  "upcoming",
-  "recent_changes",
-  "candidates",
-  "disclaimer"
-]New value: +[
+  "result",
+  "council",
+  "within_months",
+  "upcoming",
+  "upcoming_total",
+  "recent_changes",
+  "recent_changes_total",
+  "note",
+  "candidates",
+  "disclaimer"
+]
  2. Changed1 schema field changed
    • addedOutput schema / properties / upcoming / items / properties / expected_start_date / description
      Added value: +"Null where the council hasn’t announced a start date"
  3. Changed3 schema fields changed
    • addedOutput schema / properties / upcoming / items / properties / applicability
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "applies",
+        "conditional",
+        "boundary_uncertain",
+        "does_not_apply",
+        "not_covered"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Whether the postcode falls in the scheme’s area on our records, as for a scheme in force. Null where no postcode was given"
+}
    • addedOutput schema / properties / upcoming / items / properties / note
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / upcoming / items / required
      Previous value: -[
-  "scheme_name",
-  "scheme_type",
-  "council",
-  "stage",
-  "expected_start_date",
-  "end_date",
-  "summary",
-  "source_url",
-  "last_verified_at",
-  "housefile_url"
-]New value: +[
+  "scheme_name",
+  "scheme_type",
+  "council",
+  "stage",
+  "applicability",
+  "note",
+  "expected_start_date",
+  "end_date",
+  "summary",
+  "source_url",
+  "last_verified_at",
+  "housefile_url"
+]
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the safety annotations, the description discloses ordering (newest first), default and maximum month ranges, and important truncation behavior: all-council queries are capped at 15 soonest schemes and 10 latest changes with totals, while single-council queries return all. These are exactly the behavioral details an agent needs to interpret results correctly.

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 compact and front-loaded with the core purpose, then moves efficiently into filters, defaults, and result limits. Every sentence carries useful information without repetition.

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 annotations, complete parameter schema, and output schema, the description provides all the context needed to call the tool correctly. It covers purpose, temporal scope, filtering, defaults, ordering, and truncation behavior.

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 100%, so the schema documents both parameters. The description adds meaningful semantics beyond the schema by explaining that omitting the council returns all councils, with truncation limits that do not apply when a single council is requested.

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 clearly states the tool returns upcoming licensing schemes and recent changes, with a specific temporal scope and ordering. It is distinguishable from siblings by focusing on upcoming/recent change records, though it does not explicitly name alternatives.

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?

It explains the optional council filter, the default and maximum lookahead/back window, and when to ask for a single council to see full results. It gives clear usage context but does not explicitly compare against sibling tools.

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

All HouseFile UK property licensing checker toolsInspect
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