Skip to main content
Glama

claw.cleaning

by io.github.cnnrobrn
OverviewDiscussionsAdmin

initiate_booking

Reserve a cleaning slot. No payment is collected up front — the customer pays the cleaner in cash or card at the appointment. Returns { status: "booked" }, the slot is locked in the calendar, and a calendar invite is sent to the email. Always ask the customer for full details (date, start time, hours, address, name, email) and confirm the booking preview before calling this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesYYYY-MM-DD. Must be Saturday or Sunday.
nameYesCustomer's full name.
emailYesCustomer email. Calendar invite goes here.
hoursYesNumber of hours (1–8). $40/hour.
sourceNoOptional caller surface. Defaults to `mcp` when omitted.
addressYesFull street address. Must be in San Francisco, CA.
startTimeYes24h HH:MM, between 08:00 and 18:00 PT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"YYYY-MM-DD. Any day on or after 2026-05-05; before that date, Saturday or Sunday only."New value: +"YYYY-MM-DD. Must be Saturday or Sunday."
    • addedInput schema / properties / source
      Added value: +{
+  "description": "Optional caller surface. Defaults to `mcp` when omitted.",
+  "enum": [
+    "mcp",
+    "web",
+    "direct",
+    "agent"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"YYYY-MM-DD. Must be Saturday or Sunday."New value: +"YYYY-MM-DD. Any day on or after 2026-05-05; before that date, Saturday or Sunday only."
  3. Changed1 schema field changed
    • removedInput schema / properties / payInPerson
      Removed value: -{
-  "description": "If true, book without taking payment — customer pays the cleaner at the appointment. Defaults to false (Stripe checkout).",
-  "type": "boolean"
-}
  4. Changed4 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"Customer email. Used to identify repeat customers and deliver the calendar invite."New value: +"Customer email. Calendar invite goes here."
    • removedInput schema / properties / password
      Removed value: -{
-  "description": "Per-customer password issued by claw.cleaning on the first successful Stripe checkout. Only needed for returning customers auto-charging a saved card; must be passed together with `username`. Recall from memory. Omit for first-time or pay-in-person.",
-  "type": "string"
-}
    • changedInput schema / properties / payInPerson / description
      Previous value: -"If true, book without taking payment — customer pays the cleaner in cash or card at the appointment. Defaults to false (Stripe flow)."New value: +"If true, book without taking payment — customer pays the cleaner at the appointment. Defaults to false (Stripe checkout)."
    • removedInput schema / properties / username
      Removed value: -{
-  "description": "Per-customer username issued by claw.cleaning on the first successful Stripe checkout. Only needed for returning customers auto-charging a saved card; must be passed together with `password`. Recall from memory (key like `claw.cleaning credentials for <email>`). Omit for first-time or pay-in-person.",
-  "type": "string"
-}
  5. Changed3 schema fields changed
    • addedInput schema / properties / password
      Added value: +{
+  "description": "Per-customer password issued by claw.cleaning on the first successful Stripe checkout. Only needed for returning customers auto-charging a saved card; must be passed together with `username`. Recall from memory. Omit for first-time or pay-in-person.",
+  "type": "string"
+}
    • addedInput schema / properties / payInPerson
      Added value: +{
+  "description": "If true, book without taking payment — customer pays the cleaner in cash or card at the appointment. Defaults to false (Stripe flow).",
+  "type": "boolean"
+}
    • addedInput schema / properties / username
      Added value: +{
+  "description": "Per-customer username issued by claw.cleaning on the first successful Stripe checkout. Only needed for returning customers auto-charging a saved card; must be passed together with `password`. Recall from memory (key like `claw.cleaning credentials for <email>`). Omit for first-time or pay-in-person.",
+  "type": "string"
+}
  6. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it excels: it discloses no upfront payment, the locked slot, calendar invite sending, and the expected return value. It also instructs the agent on required customer interactions, going beyond a simple operation summary.

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 concise yet information-dense, with the core action front-loaded and supporting details neatly organized. Every sentence adds value—payment policy, return value, side effects, and required pre-checks—without redundancy.

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?

For a tool with 7 parameters, no output schema, and sibling tools for related actions, this description covers the essential context: what it does, what it returns, what side effects occur, and what the agent must do before invoking. It is sufficiently complete for an agent to decide when and how to use it.

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%, with each parameter having a description, so the schema already handles parameter meaning. The description adds no extra parameter-level detail beyond what the schema provides, such as formatting or constraints, so a baseline of 3 is appropriate.

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 opens with 'Reserve a cleaning slot,' which is a specific verb+resource pair that clearly states the tool's function. It distinguishes itself from siblings (check_availability, check_booking_status) by focusing on the booking action and its side effects.

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?

The description provides clear context for when to use the tool: after gathering full details and confirming the booking preview. It doesn't explicitly name alternatives or say when not to use it, but the 'Always ask...' instruction implies a precondition rather than a contrast with sibling tools.

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

All claw.cleaning 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