Skip to main content
Glama
Sign In

HomeMaster

by co.homemaster
OverviewDiscussionsAdmin

Get the exact price

get_quote
Read-onlyIdempotent

Get the price the checkout will show a new customer, with any evening rate or public voucher it applies. Give date and start_time (from find_times) for the exact figure for that slot; without them you get the price for that length or job, and the evening rate is described separately. For weekly and every-2-weeks cleans it returns both the prepaid pack of visits (what the checkout starts on) and paying per visit.

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, Singapore date.
hoursNoCleaning only: visit length in hours (see find_services for the lengths we sell, e.g. 2, 3 or 4). When the customer has not said, use usual_hours on the cleaning entry of find_services (find_times and get_quote use it when hours is left out) and say it in your proposal; do not ask. Only if they ask how long their home needs, suggest from hours_by_home.
serviceYesRequired: the code of the service the customer asked for, from find_services (e.g. cleaning, aircon, sofa_cleaning). cleaning = home cleaning by the hour, a housekeeper's work (tidying, fridge, dishes, plants, vacuuming soft furnishings included); a deep, spring or move-out clean is a home clean with more hours, and a machine deep clean of one item is its own service. Every other service is booked by the job: give job_type and unit_count from its card.
job_typeNoEvery service but cleaning: the job, a job_type from the service's card (find_services with its code), e.g. general_service for aircon. A service quoted for each job has one: its quotation visit (quotation_visit) or consultation.
frequencyNoCleaning only: one-time, weekly, or bi-weekly (every 2 weeks).one-time
start_timeNoStart time from find_times, 24-hour HH:MM (e.g. 19:30) or like 7:30 PM.
unit_countNoEvery service but cleaning: how many, in the service's own unit from its card (units, pieces, hours, panels...). 1 for a quotation visit or a consultation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / hours / description
      Previous value: -"Cleaning only: visit length in hours (see find_services for the lengths we sell, e.g. 2, 3 or 4). A customer unsure how long their home needs: the suggestion by home is hours_by_home on the cleaning entry of find_services."New value: +"Cleaning only: visit length in hours (see find_services for the lengths we sell, e.g. 2, 3 or 4). When the customer has not said, use usual_hours on the cleaning entry of find_services (find_times and get_quote use it when hours is left out) and say it in your proposal; do not ask. Only if they ask how long their home needs, suggest from hours_by_home."
  2. Changed1 schema field changed
    • changedInput schema / properties / service / description
      Previous value: -"Required: the code of the service the customer asked for, from find_services (e.g. cleaning, aircon, sofa_cleaning). cleaning = home cleaning by the hour, general housekeeping only: a deep clean, a spring clean, a move-out clean or one item cleaned is its own service. Every other service is booked by the job: give job_type and unit_count from its card."New value: +"Required: the code of the service the customer asked for, from find_services (e.g. cleaning, aircon, sofa_cleaning). cleaning = home cleaning by the hour, a housekeeper's work (tidying, fridge, dishes, plants, vacuuming soft furnishings included); a deep, spring or move-out clean is a home clean with more hours, and a machine deep clean of one item is its own service. Every other service is booked by the job: give job_type and unit_count from its card."
  3. Changed1 schema field changed
    • changedInput schema / properties / hours / description
      Previous value: -"Cleaning only: visit length in hours (see find_services for the lengths we sell, e.g. 2, 3 or 4)."New value: +"Cleaning only: visit length in hours (see find_services for the lengths we sell, e.g. 2, 3 or 4). A customer unsure how long their home needs: the suggestion by home is hours_by_home on the cleaning entry of find_services."
  4. Changed4 schema fields changed
    • changedInput schema / properties / job_type / description
      Previous value: -"Aircon only: the job, e.g. general_service, chemical_wash, chemical_overhaul (see find_services)."New value: +"Every service but cleaning: the job, a job_type from the service's card (find_services with its code), e.g. general_service for aircon. A service quoted for each job has one: its quotation visit (quotation_visit) or consultation."
    • changedInput schema / properties / service / description
      Previous value: -"Required: the service the customer asked for, from find_services. This tool checks a service booked online, one that find_services lists under services: cleaning = home cleaning by the hour (general housekeeping only; a deep clean, spring clean or move-out clean is a different service, under more_services). aircon = aircon servicing, checked here only while find_services lists it under services; while it is under more_services this tool answers with how it is booked."New value: +"Required: the code of the service the customer asked for, from find_services (e.g. cleaning, aircon, sofa_cleaning). cleaning = home cleaning by the hour, general housekeeping only: a deep clean, a spring clean, a move-out clean or one item cleaned is its own service. Every other service is booked by the job: give job_type and unit_count from its card."
    • removedInput schema / properties / service / enum
      Removed value: -[
-  "cleaning",
-  "aircon"
-]
    • changedInput schema / properties / unit_count / description
      Previous value: -"Aircon only: number of aircon units (fan coils)."New value: +"Every service but cleaning: how many, in the service's own unit from its card (units, pieces, hours, panels...). 1 for a quotation visit or a consultation."
  5. Changed1 schema field changed
    • changedInput schema / properties / service / description
      Previous value: -"Required: the service the customer asked for, from find_services. cleaning = home cleaning by the hour (general housekeeping only); aircon = aircon servicing, priced per job and number of units."New value: +"Required: the service the customer asked for, from find_services. This tool checks a service booked online, one that find_services lists under services: cleaning = home cleaning by the hour (general housekeeping only; a deep clean, spring clean or move-out clean is a different service, under more_services). aircon = aircon servicing, checked here only while find_services lists it under services; while it is under more_services this tool answers with how it is booked."
  6. Changed3 schema fields changed
    • removedInput schema / properties / service / default
      Removed value: -"cleaning"
    • changedInput schema / properties / service / description
      Previous value: -"cleaning = home cleaning by the hour; aircon = aircon servicing, priced per job and number of units."New value: +"Required: the service the customer asked for, from find_services. cleaning = home cleaning by the hour (general housekeeping only); aircon = aircon servicing, priced per job and number of units."
    • addedInput schema / required
      Added value: +[
+  "service"
+]
  7. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the burden is lower, yet the description still adds real behavior: pricing is a checkout-equivalent figure, vouchers and evening rates are folded in, and weekly/bi-weekly return both the prepaid pack and the per-visit price. It stops short of stating currency, rounding, or whether prices can change mid-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?

Four sentences, front-loaded with the core purpose, then the exact-vs-approximate rule, then the weekly/bi-weekly return shape. Dense but every clause carries operative information; nothing is repeated from the schema.

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?

With no output schema, the description must carry return-value meaning, and it does explain that weekly/bi-weekly come back with two price forms and that the evening rate is separate when no slot is given. A brief note on the returned structure or currency would close the last gap, but an agent has enough to call and interpret 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 coverage is 100%, so baseline is 3; the description goes further by explaining the interaction between parameters — date+start_time yield a slot-exact price, omitting them falls back to a length/job price — which the schema does not encode. It does not add anything about frequency or unit_count beyond the schema text.

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 ('Get the price the checkout will show a new customer') and scopes it beyond a bare lookup by naming what the figure includes (evening rate, public voucher). It is clearly distinguishable from siblings such as find_services (which supplies service codes) and find_times (which supplies slot times).

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?

Gives an explicit conditional: pass `date` and `start_time` (from find_times) for an exact slot figure, otherwise you get a length/job-level price with the evening rate described separately. It routes the agent to find_times and find_services for inputs, but does not state when not to call this tool or what to do with the two different price shapes once returned.

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

All HomeMaster toolsInspect
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