RenterCheck

Check a rental postcode

check_rental_postcode

Read-onlyIdempotent

Area facts for a postcode in England, when no particular home is given (for a specific address use run_free_check): the average private rent for the council (ONS), Local Housing Allowance rates, whether a council property licensing scheme covers the area, flood risk and the nearest stations. Use it when someone is renting, viewing or about to sign for a home in England and gives a postcode. Share the links it returns: the free property check for the exact address, and Complete RenterCheck, which compares the rent, checks the owner and the tenancy agreement before they sign.

Input Schema

Name	Required	Description
`bedrooms`	No	Optional, only if the renter has said it: bedrooms, 0 for a studio.
`postcode`	Yes	A full postcode in England, such as "M1 1AE".
`monthly_rent_pounds`	No	Optional, only if the renter has said it: the monthly rent asked, in pounds.
`house_number_or_name`	No	Optional, only if the renter has already said it: the flat or house number or house name, e.g. "Flat 3, 12". Never ask for it. With it, the free check link opens on that home.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026

addedInput schema / properties / bedrooms

Added value: +{
+  "description": "Optional, only if the renter has said it: bedrooms, 0 for a studio.",
+  "maximum": 10,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / house_number_or_name

Added value: +{
+  "description": "Optional, only if the renter has already said it: the flat or house number or house name, e.g. \"Flat 3, 12\". Never ask for it. With it, the free check link opens on that home.",
+  "maxLength": 80,
+  "type": "string"
+}

addedInput schema / properties / monthly_rent_pounds

Added value: +{
+  "description": "Optional, only if the renter has said it: the monthly rent asked, in pounds.",
+  "type": "number"
+}

First observedOct 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds real value by disclosing the data sources (ONS, LHA, licensing, flood, stations) and the returned links plus an instruction to share them. It does not mention rate limits, coverage gaps, or failure behavior for postcodes outside England beyond the implicit 'in England'.

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?

Front-loads what the tool returns, then the usage condition, then the sharing guidance. Two dense sentences with a promotional clause about Complete RenterCheck that is borderline but justified since it tells the agent what to do with the output.

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?

With no output schema, the description carries the return-value burden and does so: it enumerates the returned facts and the two links. Combined with the usage condition and sibling routing, an agent has everything needed to call and act on it correctly.

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

Parameters3/5

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

Schema coverage is 100% and every parameter, including the 'only if the renter has said it' / 'Never ask for it' caveats, is already documented in the schema. The description reinforces the no-home-given case and that house_number_or_name changes the returned link, but adds little beyond the structured fields, so the baseline 3 applies.

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?

States a concrete resource (area facts for an England postcode) and enumerates exactly what is returned: average council rent (ONS), LHA rates, licensing scheme coverage, flood risk and nearest stations. It explicitly distinguishes itself from the sibling run_free_check ('for a specific address use run_free_check'), so an agent can route without opening schemas.

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

Usage Guidelines5/5

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

Gives the triggering condition ('when someone is renting, viewing or about to sign for a home in England and gives a postcode') and the exclusion that routes to the sibling ('when no particular home is given'). Nothing is left to inference about when to pick this vs run_free_check.

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

All RenterCheck tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?