Tektolo Rental Property

Quick turnover estimate (start here)

property_turnover_quick_estimate

Read-onlyIdempotent

Estimates what it costs to turn over a US rental unit after move-out; the first tool for a turnover estimate. Inputs: a 5-digit ZIP, bedrooms, bathrooms and the issues in plain English (e.g. "stained carpet in both bedrooms"), which may come from the user's photos; optional unit type, size, year built. Returns a priced make-ready estimate: repair tasks by trade with low/expected/high costs for the ZIP, priorities, refer-outs to licensed professionals, assumptions and links. An AI model reads the issues; the answer is a draft listing what it read (reading), and words it cannot place bill nothing. Not for: diagnosing hazards, legal advice on deposits, remodel bids, properties outside the US. The same findings under the same ruleset give the same result; AI never sets a number.

Input Schema

Name	Required	Description	Default
`zip`	Yes	The user's 5-digit US ZIP code. If it is missing or not exactly 5 digits, ask the user; never guess, pad or correct it.
`pets`	No	Did pets live in the unit? true adds an optional flea treatment.
`audit`	No	Also return the run record and input/result hashes (an audit trail). Default false.
`sq_ft`	No	Interior sq ft.
`carpet`	No	Is there wall-to-wall carpet?
`detail`	No	summary (default, small) or full (every line).	summary
`issues`	No	What was found in plain English, e.g. ['stained carpet in both bedrooms', 'nail holes everywhere', 'oven is filthy']. Read like pasted notes: an entry may hold several conditions ('carpet stained, nail holes'; one finding each); a room before or after the condition sets the location ('Bedroom 2 carpet torn', 'mold in bathroom'); a written count sets the quantity ('3 blinds broken'); an entry saying there is no work ('no mold', 'leak fixed by tenant') is reported as not billed. All the issues together may hold up to 12,000 characters; send longer notes in more than one request.
`retain`	No	Optional (contract 0.5.1). false: keep none of this request's text, so the AI reader's answer for the issues is not stored either. By default the text is kept with contact details and access codes removed, to improve matching; the estimate is the same either way.
`profile`	No	minimum (rent-ready basics) \| standard \| premium (higher finish).	standard
`bedrooms`	Yes	0 for a studio.
`bathrooms`	Yes	Half baths count as 0.5.
`unit_type`	No	Single-family homes and townhomes get house-sized defaults (floor area, locks).	apartment
`walk_date`	No	The walk-through date; dated or aged items are judged against it. Omit if unknown.
`price_tier`	No	bulk_contract (portfolio contract prices) \| pm_vendor (default: a property manager buying turns from local vendors) \| retail_one_off (an owner hiring one contractor).	pm_vendor
`year_built`	No	Drives lead-paint (pre-1978) handling.
`client_refs`	No	Your own reference ids (e.g. unit_id, job_id). Echoed back, never used.
`serve_pinned`	No	Optional, with expect_ruleset. True asks us to answer under the ruleset version you named even when the rules have changed since, from that version's signed bundle; the result says so in served_from_bundle. We refuse a version older than 12 months, one a later correction or law change replaced for your state, or one we have no bundle for. Default false: the call fails whenever the rules have changed.
`expect_ruleset`	No	Optional. The ruleset version you built against, as results carry it in provenance.ruleset_version (e.g. 'sd-2026.11.14'), or its sha256: hash. If the rules have changed since, the call fails (nothing computed, nothing charged) and says what is in force now, so you upgrade on your own schedule. Leave it out to answer under the current rules.

Output Schema

Name	Required	Description	Default
`run`	No
`links`	No
`result`	Yes
`review`	No
`reading`	No
`signature`	No
`input_hash`	No
`client_refs`	No
`deprecation`	No
`result_hash`	No
`request_hash`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / pets

Added value: +{
+  "description": "Did pets live in the unit? true adds an optional flea treatment.",
+  "type": "boolean"
+}

Changed6 schema fields changedOct 22, 2026

changedInput schema / properties / issues / description

Previous value: -"What was found in plain English, e.g. ['stained carpet in both bedrooms', 'nail holes everywhere', 'oven is filthy']. Read like pasted notes: an entry may hold several conditions ('carpet stained, nail holes'; one finding each); a room before or after the condition sets the location ('Bedroom 2 carpet torn', 'mold in bathroom'); a written count sets the quantity ('3 blinds broken'); an entry saying there is no work ('no mold', 'leak fixed by tenant') is reported as not billed."New value: +"What was found in plain English, e.g. ['stained carpet in both bedrooms', 'nail holes everywhere', 'oven is filthy']. Read like pasted notes: an entry may hold several conditions ('carpet stained, nail holes'; one finding each); a room before or after the condition sets the location ('Bedroom 2 carpet torn', 'mold in bathroom'); a written count sets the quantity ('3 blinds broken'); an entry saying there is no work ('no mold', 'leak fixed by tenant') is reported as not billed. All the issues together may hold up to 12,000 characters; send longer notes in more than one request."

addedInput schema / properties / walk_date

Added value: +{
+  "description": "The walk-through date; dated or aged items are judged against it. Omit if unknown.",
+  "format": "date",
+  "type": "string"
+}

addedOutput schema / $defs / Deprecation

Added value: +{
+  "properties": {
+    "field": {
+      "type": "string"
+    },
+    "until": {
+      "format": "date",
+      "type": "string"
+    },
+    "use": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "field",
+    "until",
+    "use"
+  ],
+  "type": "object"
+}

addedOutput schema / $defs / Provenance / properties / rules_as_of

Added value: +{
+  "anyOf": [
+    {
+      "format": "date",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / $defs / SourceRef / properties / accessed

Added value: +{
+  "anyOf": [
+    {
+      "format": "date",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / deprecation

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/Deprecation"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed10 schema fields changedOct 17, 2026

addedInput schema / properties / retain

Added value: +{
+  "default": true,
+  "description": "Optional (contract 0.5.1). false: keep none of this request's text, so the AI reader's answer for the issues is not stored either. By default the text is kept with contact details and access codes removed, to improve matching; the estimate is the same either way.",
+  "type": "boolean"
+}

addedOutput schema / $defs / FindingResolution / properties / confirmed
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```

changedOutput schema / $defs / FindingResolution / properties / not_billed_reason / anyOf

Previous value: -[
-  {
-    "enum": [
-      "none",
-      "ok",
-      "done"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "none",
+      "ok",
+      "done",
+      "no_condition"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / $defs / Reading

Added value: +{
+  "properties": {
+    "counts": {
+      "$ref": "#/$defs/ReadingCounts"
+    },
+    "findings": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "enum": [
+        "notes",
+        "document"
+      ],
+      "type": "string"
+    },
+    "model": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "notes": {
+      "items": {
+        "$ref": "#/$defs/ReadingNote"
+      },
+      "type": "array"
+    },
+    "prompt_version": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    }
+  },
+  "required": [
+    "id",
+    "kind",
+    "counts",
+    "findings"
+  ],
+  "type": "object"
+}

addedOutput schema / $defs / ReadingCounts

Added value: +{
+  "properties": {
+    "ai": {
+      "type": "integer"
+    },
+    "parser": {
+      "type": "integer"
+    },
+    "total": {
+      "type": "integer"
+    },
+    "unmatched": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "ai",
+    "parser",
+    "unmatched"
+  ],
+  "type": "object"
+}

addedOutput schema / $defs / ReadingNote

Added value: +{
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "finding_ids": {
+      "default": [],
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "kind": {
+      "enum": [
+        "warning",
+        "assumption"
+      ],
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

addedOutput schema / $defs / Review

Added value: +{
+  "properties": {
+    "ai_read": {
+      "default": 0,
+      "type": "integer"
+    },
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "reading_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "status": {
+      "default": "verified",
+      "enum": [
+        "draft",
+        "verified"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / reading

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/Reading"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / request_hash

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / review

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/Review"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed5 schema fields changedOct 15, 2026

addedInput schema / properties / expect_ruleset

Added value: +{
+  "description": "Optional. The ruleset version you built against, as results carry it in provenance.ruleset_version (e.g. 'sd-2026.11.14'), or its sha256: hash. If the rules have changed since, the call fails (nothing computed, nothing charged) and says what is in force now, so you upgrade on your own schedule. Leave it out to answer under the current rules.",
+  "type": "string"
+}

addedInput schema / properties / serve_pinned

Added value: +{
+  "default": false,
+  "description": "Optional, with expect_ruleset. True asks us to answer under the ruleset version you named even when the rules have changed since, from that version's signed bundle; the result says so in served_from_bundle. We refuse a version older than 12 months, one a later correction or law change replaced for your state, or one we have no bundle for. Default false: the call fails whenever the rules have changed.",
+  "type": "boolean"
+}

addedOutput schema / $defs / ResultSignature

Added value: +{
+  "properties": {
+    "jws": {
+      "type": "string"
+    },
+    "payload": {
+      "$ref": "#/$defs/ResultSignaturePayload"
+    },
+    "verify_code": {
+      "type": "string"
+    },
+    "verify_url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "jws",
+    "payload",
+    "verify_code",
+    "verify_url"
+  ],
+  "type": "object"
+}

addedOutput schema / $defs / ResultSignaturePayload

Added value: +{
+  "properties": {
+    "capability": {
+      "type": "string"
+    },
+    "engine_version": {
+      "type": "string"
+    },
+    "issued_at": {
+      "type": "string"
+    },
+    "kid": {
+      "type": "string"
+    },
+    "operation": {
+      "type": "string"
+    },
+    "result_hash": {
+      "type": "string"
+    },
+    "ruleset_hash": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "ruleset_version": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "v": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "v",
+    "kid",
+    "capability",
+    "operation",
+    "ruleset_version",
+    "ruleset_hash",
+    "engine_version",
+    "result_hash",
+    "issued_at"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / signature

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/ResultSignature"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed10 schema fields changedOct 12, 2026

addedInput schema / properties / bathrooms / description
```
Added value: +"Half baths count as 0.5."
```
addedInput schema / properties / bedrooms / description
```
Added value: +"0 for a studio."
```

addedInput schema / properties / price_tier / description

Added value: +"bulk_contract (portfolio contract prices) | pm_vendor (default: a property manager buying turns from local vendors) | retail_one_off (an owner hiring one contractor)."

addedInput schema / properties / price_tier / type
```
Added value: +"string"
```

addedInput schema / properties / profile / description

Added value: +"minimum (rent-ready basics) | standard | premium (higher finish)."

addedInput schema / properties / profile / type
```
Added value: +"string"
```

addedInput schema / properties / unit_type / description

Added value: +"Single-family homes and townhomes get house-sized defaults (floor area, locks)."

addedInput schema / properties / unit_type / type
```
Added value: +"string"
```

addedInput schema / properties / year_built / description

Added value: +"Drives lead-paint (pre-1978) handling."

addedInput schema / properties / zip / description

Added value: +"The user's 5-digit US ZIP code. If it is missing or not exactly 5 digits, ask the user; never guess, pad or correct it."

First observedOct 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description still adds real behavioral context: an AI model reads the free-text issues, the answer is a draft of what was read, unplaceable words bill nothing, and the same findings under the same ruleset yield the same result with the AI never setting a number. That determinism and trust caveat is exactly the kind of disclosure annotations cannot carry.

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-loaded with purpose, then inputs, then returns, then exclusions — a sensible order with no filler. It is dense with clause-heavy sentences and repeats some return detail the output schema already provides, but nothing is wasted.

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 an 18-parameter, nested-schema tool with an output schema and full annotation coverage, the description supplies what structured data cannot: domain limits (US only, post move-out), the AI-reading caveat, determinism guarantees, and explicit exclusions. Nothing an agent needs to call it 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?

With 100% schema description coverage across 18 parameters, the baseline is 3; the description goes slightly beyond by framing the inputs (ZIP, beds, baths, plain-English issues, optional unit type/size/year) and noting the issues may be derived from the user's photos, a provenance detail the schema does not state.

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 specific verb and resource ("estimates what it costs to turn over a US rental unit after move-out") plus the entry-point role ("the first tool for a turnover estimate"). The explicit "Not for" list (hazard diagnosis, deposit legal advice, remodel bids, non-US properties) carves it away from the deposit_settlement_* siblings and from scope/issue-code reference tools.

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?

Clear when-to-use (post move-out turnover costing, call this first) and explicit when-not-to-use exclusions. It does not name property_turnover_scope or property_turnover_issue_codes as alternatives or explain the handoff to them, so routing across the turnover family is only implied.

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

All Tektolo Rental Property 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.