Skip to main content
Glama

HomeMaster

by co.homemaster
OverviewDiscussionsAdmin

Start a booking (returns a filled-in checkout link)

start_booking
Read-onlyIdempotent

Get a link to HomeMaster's checkout with the address and the visit already filled in, to give to the customer. Nothing is booked or charged by this tool. On the page the customer picks the start time (it is held for 7 minutes), enters their name and phone, types the 6-digit code we send to their WhatsApp, and pays on our payment page. Never pay on the customer's behalf. For a service booked by the job the link opens that service's checkout: give the job_type and unit_count the customer agreed to and the page starts on them (they can still change them). To book a home clean FOR the customer instead, use request_booking: they confirm with one tap on WhatsApp.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
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.
postal_codeYes6-digit Singapore postal code, e.g. 238823.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / job_type
      Added value: +{
+  "description": "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.",
+  "type": "string"
+}
    • 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"
-]
    • addedInput schema / properties / unit_count
      Added value: +{
+  "description": "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.",
+  "minimum": 1,
+  "type": "integer"
+}
  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."
    • changedInput schema / required
      Previous value: -[
-  "postal_code"
-]New value: +[
+  "postal_code",
+  "service"
+]
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), and the description is consistent with them while adding real context beyond them: 'Nothing is booked or charged by this tool,' a 7-minute hold on the start time, the customer's steps (code via WhatsApp, payment page), and the guardrail 'Never pay on the customer's behalf.'

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?

Front-loads the outcome (the filled-in checkout link) and the key reassurance (nothing booked or charged), then proceeds to the customer flow and the alternative. It is dense but long, with the page-step narration being the one stretch that could be tightened without losing meaning.

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?

No output schema exists, and the description fully compensates by explaining that the return is a checkout link to hand to the customer, what the customer does with it, and the two branches (hourly cleaning vs. job-based with job_type/unit_count). Nothing needed to call it correctly is missing.

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 parameters are already documented (baseline 3), but the description adds behavioral meaning the schema cannot: job_type and unit_count pre-fill the checkout page for job-based services and the customer 'can still change them.' That clarifies how parameters actually behave rather than just what they are.

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+resource: 'Get a link to HomeMaster's checkout with the address and the visit already filled in.' It immediately clarifies the artifact produced and explicitly distinguishes itself from the sibling request_booking, so an agent can pick it without opening the schema.

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?

Names the alternative in-line ('To book a home clean FOR the customer instead, use request_booking') with the condition that selects it, and states when in the flow to hand the link to the customer. When-to-use and when-to-use-something-else are both explicit.

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