rentready
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_propertyA | 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. |
| check_portfolioA | Check many English rental properties at once for the landlord database. Input is CSV text (header row: name, postcode, gas, no_gas, eicr, eicr_due, epc, epc_rating, tenancy_start, region) or a JSON list of objects with those keys. Returns one line per property, the total £65/property fee, the earliest deadline and every FAIL/WARN. |
| make_calendarA | Build an iCalendar (.ics) file for one property or a portfolio: registration window opens, registration deadline, and each gas/EICR/EPC expiry as all-day events with reminders. Save the returned text as rentready.ics and import it into Google, Apple or Outlook calendar. |
| registration_packA | Prepare the registration pack for England's 'Register your rental property' service: every question the service asks (landlord, dwelling, tenancy, rent, health and safety), pre-filled from the portfolio where known and marked GATHER where not, and each certificate to scan with a suggested file name, flagging any that must be renewed before upload. Returns a markdown checklist. Extra optional columns: bedrooms, dwelling_type, ownership, let, occupants, households, licence, furnished, rent, rent_frequency, bills, freeholder, manager. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The two bulk/single variants (check_property vs check_portfolio) are clearly differentiated by input shape, but registration_pack and check_property overlap substantially: both report the registration window, fee, certificate validity and an upload checklist for a single property, so an agent could reasonably pick either one when asked 'is this property ready to register?'.
Three of four tools follow a clean verb_noun snake_case pattern (make_calendar, check_property, check_portfolio), and registration_pack is the lone noun-only outlier. The deviation is readable and the prefix split (single vs portfolio) is discoverable.
Four tools is compact and each maps to a distinct deliverable (pack, calendar, single check, batch check), with no filler. It sits at the low end of the comfortable range but is well matched to a narrow compliance-lookup purpose.
The surface covers preparation, checking and scheduling, but there is no operation to record or persist property data, update certificate details, or track remediation status after a FAIL, so the agent hits a dead end once it leaves the advisory flow. The domain itself is clearly stated and core questions are answerable.