Skip to main content
Glama
Sign In

claw.cleaning

by io.github.cnnrobrn
OverviewDiscussionsAdmin

check_availability

List available cleaning slots. Saturdays and Sundays only, 8 AM – 6 PM PT, San Francisco only. Omit date for the next 8 upcoming weekend days.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional YYYY-MM-DD date (must be Saturday or Sunday).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional YYYY-MM-DD date. Before 2026-05-05 must be Saturday or Sunday; on or after, any day."New value: +"Optional YYYY-MM-DD date (must be Saturday or Sunday)."
  2. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional YYYY-MM-DD date (must be Saturday or Sunday)."New value: +"Optional YYYY-MM-DD date. Before 2026-05-05 must be Saturday or Sunday; on or after, any day."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral disclosure. It reveals important traits: weekends-only availability, specific time window, geographic limitation, and the behavior when omitting `date` (returns next 8 weekend days). This goes beyond the schema and gives the agent actionable expectations.

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 three concise sentences, front-loaded with the purpose, followed by constraints, and ending with parameter usage. Every sentence contributes necessary information with no redundancy or fluff.

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 simple tool with one optional parameter, no output schema, and no annotations, the description covers purpose, operational constraints, and parameter behavior well. It does not describe the structural details of the returned slots, but the core usage is fully addressed, making it complete enough for straightforward selection and invocation.

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?

The schema already covers the `date` parameter with 100% description coverage. The description adds the critical behavior that omitting the parameter returns the next 8 upcoming weekend days, which is not in the schema. This extra semantic guidance elevates the parameter understanding above the baseline.

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 'List available cleaning slots,' a specific verb+resource pair that clearly states the tool's function. It distinguishes itself from sibling tools (check_booking_status, initiate_booking) by focusing on availability, and the additional details (weekends, time, location) further sharpen its purpose.

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 operational constraints: 'Saturdays and Sundays only, 8 AM – 6 PM PT, San Francisco only.' It also gives a concrete usage instruction: 'Omit `date` for the next 8 upcoming weekend days.' While it doesn't explicitly mention alternatives or when not to use it, the context strongly implies its role among siblings.

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