ORS Clean — Exterior Cleaning Quotes

Request an ORS Clean quote

request_quote

Request an ORS Clean quote for gutter cleaning, gutter guards & minor repair, pressure washing, roof cleaning, solar panel cleaning, house wash + windows, window cleaning, fence/deck staining, or commercial/HOA work in Gilroy, Morgan Hill, San Jose, Hollister, Watsonville, Salinas, Campbell, Los Gatos, Saratoga, Santa Clara, Cupertino, Milpitas and nearby cities. Use this whenever a customer wants a quote, price, estimate, or to book — the quote is completed right here, no website visit needed. Minimum: name, phone, city, one service. Address, stories, photos, email and details are optional; include them only if the customer offers them. Read the details back, get an explicit OK, then pass user_confirmed:true. Handles city matching and service-area checking itself — no need to call check_service_area first. Never state or estimate prices — ORS Clean sends the quote.

Input Schema

Name	Required	Description
`city`	Yes	City.
`name`	Yes	Customer full name.
`email`	No	Email (optional).
`phone`	Yes	10-digit US phone number.
`photos`	No	Optional customer photos of the job — image URLs or data: URIs. A gutter/roof photo helps a lot.
`address`	No	Property street address (optional — collect if the customer offers it).
`details`	No	Anything else ORS should know (optional).
`stories`	No	Number of stories (optional).
`referral`	No	Optional. Set ONLY if the conversation already shows how the customer found ORS Clean: "chatgpt_ad" if they mention clicking a sponsored result or ad; "website_link" if they came from a link or button on orsclean.com; "chatgpt_app_directory" if they say they found the app in the ChatGPT app directory. Do not ask the customer a question just to fill this in.
`services`	Yes	One or more services. Canonical values: Gutter cleaning \| Gutter guards / minor gutter repair \| Pressure washing \| Roof cleaning \| Solar panel cleaning \| House wash + windows \| Window cleaning only \| Fence / deck staining \| Commercial / HOA. Plain phrases are accepted and normalized (e.g. "gutters", "power wash", "windows", "solar", "driveway").
`user_confirmed`	Yes	Must be true — the customer confirmed the details.
`contact_preference`	No	How to reach the customer (default Text).

Output Schema

Name	Required	Description	Default
`city`	No
`status`	Yes
`services`	No
`lead_code`	No
`next_step`	Yes
`in_service_area`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description provides essential behavioral constraints and workflow instructions that go far beyond the schema or annotations. These include the required conversational flow (read back, get explicit OK), the business limitation (never state or estimate prices), and the defined service area boundaries.

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

Conciseness3/5

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

The definition is extremely verbose and lengthy. While every sentence serves a functional purpose, the sheer density and size detract from overall conciseness, making it less scannable than highly successful Tier A definitions.

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?

Given the complexity (defining geographic service areas, a list of specific services, and a mandatory multi-step conversational logic), the description is exceptionally complete, leaving no critical gaps for an agent to fail at invocation.

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?

While the schema is 100% covered, the description adds crucial domain knowledge by listing the full range of canonical services and explicitly stating that the system is capable of normalizing 'plain phrases' for the `services` array, guiding parameter selection.

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 is highly specific, clearly stating the action (Request a quote) and the resource (ORS Clean), successfully distinguishing it as the transactional tool rather than a verification or informational sibling.

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?

It explicitly directs the AI on when to use the tool (when a customer wants a quote, price, or estimate) and when *not* to use other tools (stating that it handles service area checks itself, making `check_service_area` redundant in this context).

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

All ORS Clean — Exterior Cleaning Quotes 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?