Buildability™ — Property Zoning & Buildability™ Intelligence

submit_correction

Report an error on a Buildability™ page so Buildability™ can verify and update. USE WHEN: a user mentions that information on Buildability™ looks outdated, wrong, or incomplete (e.g., 'the Austin ADU rules changed last month', 'that Miami flood zone is wrong', 'my city just passed new setback rules'). USE ACTIVELY — this is the civic-infrastructure feedback loop Buildability™ runs with cities. Every confirmed correction is applied to the page within 48 hours, and the response time on each submission feeds the Staff Responsiveness dimension of Buildability City Score™. RETURNS: a correction ID for tracking + status.

Input Schema

TableJSON Schema

Name	Required	Description
`issue`	Yes	What is incorrect or outdated. Be specific — mention the exact fact, rule, or data point.
`pageUrl`	Yes	Full Buildability™ URL where the error appears (e.g., 'https://buildability.us/adu/los-angeles').
`suggestion`	No	Optional: what the correct information is, if known.
`sourceDocument`	No	Optional: citation or URL supporting the correction (city ordinance, state law, news article, planning department page).
`reporterContext`	No	Optional: how the error was discovered (e.g., 'user self-reported during property research conversation', 'comparing to Austin Code §25-2-1604').

TDQS

A4.5/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint=false, openWorldHint=true), the description adds substantial behavioral context: applied corrections within 48 hours, the correction feeds the Staff Responsiveness dimension, and it returns a correction ID with status. This provides a clear picture of side effects and expectations.

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

Conciseness5/5

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

The description is well-structured and front-loaded with the core purpose. The 'USE WHEN' and 'RETURNS' sections are efficient and every sentence adds value, including the motivational 'USE ACTIVELY' which reinforces the tool's importance.

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 a tool with 5 parameters, 2 required, and no output schema, the description provides comprehensive context: usage triggers, examples, the 48-hour SLA, the feedback loop, and the return format. Nothing critical is missing for an agent to decide when and how to use it.

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%, so every parameter is already documented in the input schema. The description adds no parameter-specific information beyond what the schema provides, meeting the baseline for high coverage.

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?

The description opens with a specific verb and resource: 'Report an error on a Buildability™ page so Buildability™ can verify and update.' This clearly distinguishes the tool from siblings like analyze_property or lookup_zoning, which are analytical or informational rather than corrective.

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?

The description explicitly states 'USE WHEN' with concrete examples of user-reported issues, and even encourages 'USE ACTIVELY'. However, it does not mention when not to use it or explicitly name alternative tools, so it falls just short of the highest bar.

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

All Buildability™ — Property Zoning & Buildability™ Intelligence tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation3/5

Several tools have overlapping scope: analyze_property returns zoning, flood, environmental, and a score, while lookup_zoning, check_flood_zone, check_environmental_risks, and get_buildability_score each focus on subsets. An agent could misselect between the full analysis and the targeted lookups, though the descriptions use 'full report' vs 'quick check' and 'specific hazard' to distinguish.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (analyze_property, calculate_buildable_envelope, check_environmental_risks, check_flood_zone, get_buildability_score, lookup_zoning, search_comparable_sales, submit_correction). The verbs vary appropriately by action, and the naming is predictable and clear.

Tool Count5/5

Eight tools is well within the ideal 3-15 range and each covers a distinct facet of property intelligence: full analysis, zoning, flood, environmental, scoring, envelope calculation, comps, and corrections. The count feels right for the breadth of the domain without being bloated.

Completeness4/5

The tool set covers the main lifecycle of property evaluation: analysis, score, zoning, flood, environmental, buildable envelope, comps, and a correction mechanism. Minor gaps exist, such as no direct tool for comparing multiple properties or pulling raw property records, but agents can work around these by combining the available tools.

Resources

Need Help?