Skip to main content
Glama

check_property

Check whether an English rental property is ready for the landlord database. Get the registration window and deadline, gas, EICR and EPC validity, fees, upload checklist and penalties.

Instructions

Is an English rental property ready for the landlord database (Register your rental property, Renters' Rights Act)? Returns the region's registration window and deadline, whether the gas safety record, EICR and EPC will still be valid, the £65/property fee, the upload checklist and the penalties.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
epcNoEPC issue date YYYY-MM-DD
gasNoGas safety record issue date YYYY-MM-DD
eicrNoEICR issue date YYYY-MM-DD
no_gasNoTrue if the property has no gas supply
regionNoOverride region, e.g. 'London', if no postcode
eicr_dueNoDate the EICR gives for the next inspection YYYY-MM-DD (used instead of issue + 5 years; give it whenever the report has one)
postcodeNoProperty postcode (England)
epc_ratingNoEPC rating letter A-G
propertiesNoNumber of properties, for the fee
tenancy_startNoCurrent tenancy start date YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.1
    • addedInput schema / properties / eicr_due
      Added value: +{
      +  "description": "Date the EICR gives for the next inspection YYYY-MM-DD (used instead of issue + 5 years; give it whenever the report has one)",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well by disclosing the returned checks: registration window, deadline, gas/EICR/EPC validity, fee, upload checklist, and penalties. It implies a read-only check through 'Returns' and 'check', but does not explicitly state side-effect behavior, authentication needs, or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded and dense: the purpose appears in the opening question and the return contents are summarized efficiently in the second sentence. There is no filler, though the question phrasing is slightly less direct than a declarative purpose statement.

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?

There is no output schema, so the description appropriately enumerates the key returned results. Combined with full parameter descriptions, an agent has enough to invoke the tool correctly, though the description could do more to explain output structure or when to prefer sibling tools.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already well documented in the input schema. The description mentions the relevant domains (EPC, gas, EICR, fee, region) but adds no syntax, format, or conditional guidance beyond what the schema provides.

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 identifies a readiness-checking tool for English rental properties and enumerates what it returns, including registration windows, document validity, fees, and penalties. It is specific about the resource and evaluation, but it does not explicitly distinguish itself from sibling tools such as check_portfolio or registration_pack.

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

Usage Guidelines2/5

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

The question format implies that the tool checks readiness, but there is no explicit guidance on when to use it versus alternatives. No siblings are mentioned, and there are no conditions, prerequisites, or exclusions stated.

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