Skip to main content
Glama
Sign In

HomeMaster

by co.homemaster
OverviewDiscussionsAdmin

Check whether HomeMaster covers an address

check_area
Read-onlyIdempotent

Check whether a service is available at a Singapore postal code, before looking for times. Coverage depends on which of our people or partners work near the address.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. Changed2 schema fields changed
    • 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"
-]
  3. 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."
  4. 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"
+]
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world safety, so the bar is lower; the description adds genuine context that coverage is staff/partner-proximity based and therefore approximate near boundaries. It does not say what the response looks like (boolean vs. area reference) despite there being no output schema, which is the remaining gap.

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?

Two short sentences, the primary action is front-loaded, and the caveat follows as supporting context. No redundant restatement of the title or 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?

For a 2-parameter read-only check with full schema coverage and annotations, the description supplies the purpose, sequencing, and the key caveat. Only the shape of the result (a yes/no coverage answer vs. something richer) is left unstated.

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 coverage is 100% and the service parameter is documented in far more detail than the description provides. The description only reinforces that postal_code is Singapore-specific, adding little beyond the schema's pattern and example.

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: check whether a service is covered at a Singapore postal code. The clause 'before looking for times' distinguishes it from find_times, so an agent can route without opening either schema.

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?

'before looking for times' gives explicit sequencing guidance relative to the sibling find_times. It stops short of stating when the answer is a hard stop versus a soft signal, or when find_services should precede it, so no full when/when-not pair.

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