Skip to main content
Glama

Sweepless in Seattle

Request a cleaning quote

request_quote

Send a house cleaning quote request to Sweepless in Seattle for a customer who asked for one. Covers Seattle, the Eastside and the South Sound. The request goes straight into the business scheduling system, and they reply to the customer with a flat, upfront price within one business day. Confirm the details with the customer before calling, and call once per quote.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "street": "<street>",
      "zip": "<zip>",
      "service": "<service>",
      "customer_consent": "<customer_consent>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit ZIP code.
cityNoCity, for example Seattle, Bellevue, Kirkland.
nameYesCustomer full name.
emailNoCustomer email. At least one of email or phone is required.
phoneNoCustomer US phone number, any format. At least one of email or phone is required.
streetYesStreet address of the place to be cleaned, including unit number.
detailsNoAnything else that affects the price or the visit: pets, parking, access, areas to focus on.
serviceYesrecurring = Recurring home cleaning; deep = Deep cleaning; move = Move-in / move-out cleaning; rental_turnover = Airbnb / rental turnover; apartment = Apartment or condo cleaning; office = Office / commercial cleaning; other = Other / not sure
bedroomsNoNumber of bedrooms. Use 0 for a studio.
bathroomsNoHalf baths count as 0.5.
frequencyNoone_time = One time; weekly = Weekly; biweekly = Every two weeks; monthly = Monthly
square_feetNoApproximate finished floor area of the home in square feet. A rough estimate is fine.
customer_consentYesSet to true only if the customer asked you to request this quote and agreed to be contacted about it by phone, text, or email.
preferred_timingNoWhen the customer would like the cleaning, in their words, for example "a Saturday in mid-November".

Output Schema

NameRequiredDescriptionDefault
statusYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a non-read-only, open-world, non-idempotent, non-destructive call. The description adds useful behavior beyond that: the request enters the business scheduling system, the customer receives a flat upfront price within one business day, and the agent should call only once per quote.

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 front-loaded with the action and recipient, then adds service area, business outcome, and operational constraints in four tight sentences. Every sentence contributes useful context without repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter write tool with an output schema, the description gives the essential business context: who to call for, coverage area, consent prerequisite, one-call-per-quote rule, and expected turnaround. It does not explain failure handling or out-of-area behavior, but the core invocation context is sufficiently complete.

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 description coverage is 100%, so the input schema already documents all 14 parameters, including enums, required consent, and contact requirements. The description reinforces customer consent and confirming details, but adds no parameter-specific syntax or format beyond the schema.

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 states a specific verb and resource: sending a house cleaning quote request to Sweepless in Seattle. It also identifies the service area, so the agent knows exactly what business action this tool performs.

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?

It clearly says to use this for a customer who asked for a quote, to confirm details with the customer first, and to call once per quote. Coverage is limited to Seattle, the Eastside and the South Sound, though it does not explicitly state what to do for customers outside that area.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources