Tektolo Rental Property

Scope a property turnover

property_turnover_scope

Read-onlyIdempotent

Turns move-out inspection findings for a US rental unit into a priced make-ready scope. For a first estimate use property_turnover_quick_estimate; use this one for rate cards, owner decisions or measured quantities. Inputs: property (ZIP, bedrooms, bathrooms; optional unit type, size, year built) and findings (a description or issue code, with location, extent and quantity); optional rate_card, decisions and detail. Returns tasks by trade with low/expected/high costs for the ZIP, priorities, vendor scopes, refer-outs to licensed professionals, assumptions, unknowns and download links. Not for: diagnosing hazards, legal advice on deposits, remodel bids, properties outside the US. Deterministic and source-cited: the same input gives the same result.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`audit`	No	Also return the run record and input/result hashes (an audit trail). Default false.
`detail`	No	summary: totals, trade scopes, every line tied to a finding (capped at 40) plus the largest must-fix/refer-out lines, a one-line note on the routine lines left out, notes, and only findings needing attention (small). full: every line, finding and source.	summary
`retain`	No	Optional (contract 0.5.0). false: keep none of this request's text. By default the finding descriptions are kept with contact details and access codes removed, to improve matching; the estimate is the same either way.
`findings`	No	Move-out inspection findings, one per condition, with location and extent.
`property`	Yes	The unit: ZIP, size, type and year built.
`tax_rate`	No	Applied to all lines, e.g. 0.07.
`decisions`	No	Approve, decline or defer lines or findings from an earlier scope.
`rate_card`	No	Your own prices by trade or task; they replace the regional library prices.
`standards`	No	Finish profile, price tier and overrides.
`client_refs`	No	Your own reference ids (e.g. unit_id, job_id). Echoed back, never used.
`constraints`	No	Target ready date, whether the unit is occupied, access notes.
`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.
`trade_vendors`	No	Vendor (name, contact) to put on each trade's lines.
`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

TableJSON Schema

Name	Required	Description	Default
`run`	No
`links`	No
`result`	Yes
`signature`	No
`input_hash`	No
`client_refs`	No
`result_hash`	No

Schema Changelog

Changes observed during successful MCP inspections.

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
+}

First observedOct 15, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and side-effect profile is covered. The description adds genuinely new behavior: deterministic, source-cited results, refer-outs to licensed professionals, and assumptions/unknowns surfaced in the output. It stops short of discussing limits on input size (200 findings, 300 rate-card entries) which live only in the schema.

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 and sibling routing, then inputs, returns, exclusions and a determinism note; each block earns its place. The final 'Deterministic and source-cited' sentence is slightly redundant with idempotentHint and could be folded into the returns sentence.

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 an output schema present, the description need not enumerate return fields, and it correctly summarizes them (tasks by trade, low/expected/high costs, priorities, vendor scopes, refer-outs, assumptions, unknowns, download links). Combined with rich annotations and complete schema coverage, an agent has everything needed to call this correctly.

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 description coverage is 100%, so the baseline is 3. The description goes modestly beyond by grouping the 14 flat parameters into a mental model (property vs. findings vs. optional rate_card/decisions/detail) and flagging which property fields are required vs. optional, which helps an agent plan a call.

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+resource+output: turning move-out inspection findings for a US rental unit into a priced make-ready scope. It explicitly distinguishes itself from property_turnover_quick_estimate and names the conditions that select this tool, so an agent can route without opening either schema.

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?

Explicit routing: 'For a first estimate use property_turnover_quick_estimate; use this one for rate cards, owner decisions or measured quantities.' It also lists exclusions under 'Not for' (hazard diagnosis, deposit legal advice, remodel bids, non-US properties). Both when-to-use and when-not-to-use are covered.

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.

Resources

Need Help?