Jerome Handy Wash

Published wash and dryer times

get_cycle_times

Read-onlyIdempotent

Published quick, normal and heavy wash cycle times, typical drying time and dryer minutes purchased at each starting price and per extra quarter, in English or Spanish. These are site facts, not live machine timers or a drying guarantee.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

Name	Required	Description	Default
`language`	No	Which language of the site to quote: "en" (default) or "es" (the Spanish pages, under /es/).

Output Schema

Name	Required	Description	Default
`url`	Yes
`dryers`	Yes
`notice`	Yes
`pricing`	Yes
`language`	Yes
`cycleTimes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: this is static published material, not real-time telemetry, and drying times are not guaranteed. It does not discuss caching or how often site facts change, which would have completed the picture.

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 sentences, both load-bearing: the first enumerates returned content, the second sets expectations and scope. The content list is front-loaded and nothing is padded or repeated.

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 one-parameter read-only tool with an output schema, the description covers what the agent needs: what comes back, that it is static rather than live, and that the results are informational. Return-value formatting is correctly left to the output schema.

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 single language parameter is fully documented in the schema, including the enum and the /es/ note. The description's 'in English or Spanish' restates that without adding syntax or default behavior beyond what the schema already says, so the baseline of 3 applies.

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 names the exact data returned: quick/normal/heavy wash cycle times, typical drying time, and dryer minutes per starting price and per extra quarter. That level of specificity lets an agent distinguish it from get_pricing (cost structure) and get_machines (machine inventory) 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?

The closing sentence 'These are site facts, not live machine timers or a drying guarantee' effectively tells the agent when this tool is and isn't appropriate, routing live-status questions elsewhere. It stops short of naming the alternative sibling (e.g., get_machines) explicitly, so the exclusion is implied rather than directed.

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

All Jerome Handy Wash tools Inspect

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

Need Help?