Skip to main content
Glama

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

TableJSON 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).
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, 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.
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. 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."
  2. 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."
  3. 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"
+]
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: the evening rate and public voucher adjustments applied, and that weekly/bi-weekly returns both the prepaid pack and per-visit pricing. It stops short of stating currency or whether quotes are guaranteed to hold at booking time.

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?

Three sentences, all substantive and front-loaded with the returned value before the parameter guidance. Slightly dense with parentheticals, but nothing is redundant or wasted.

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 carries the return-value burden and does describe the response shape (single slot price vs length/job price, separate evening rate, prepaid pack + per-visit pair). Currency and quote validity are the only meaningful omissions for a 7-param pricing tool.

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 the baseline is 3, but the description adds combinational semantics the schema cannot express: date is only meaningful together with start_time, and that pair yields the exact slot price while individual params give an approximation. It also stresses service is required and sourced from find_services.

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 immediately narrows scope against siblings by naming find_times as the source of date/start_time. An agent can tell this is a read-only pricing lookup distinct from find_services/find_times/request_booking.

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 explicitly tells the agent the two calling modes: pass date + start_time for the exact slot figure, or omit them to get a length/job price with the evening rate described separately. It also routes to find_times for valid slot values, though it never states when NOT to call it or how it relates to request_booking/start_booking.

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