Wash Bodega Service Discovery

Get Wash Bodega services

get_washbodega_services

Read-onlyIdempotent

Return verified public Wash & Fold and pickup/delivery availability in English or Spanish, plus the HTML pages that explain them. Read only; never collects personal data or creates an order. Rates stay on get_washbodega_pricing.

Input Schema

Name	Required	Description	Default
`locale`	No		en-US

Output Schema

Name	Required	Description	Default
`locale`	Yes
`services`	Yes
`sourceUrl`	Yes
`boundaries`	Yes
`publishedAt`	Yes
`readingPages`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

addedOutput schema / properties / readingPages / properties / petGuide
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
addedOutput schema / properties / readingPages / properties / petToolkit
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```

changedOutput schema / properties / readingPages / required

Previous value: -[
-  "washFold",
-  "pickupDelivery",
-  "comparison",
-  "caregiverToolkit"
-]New value: +[
+  "washFold",
+  "pickupDelivery",
+  "comparison",
+  "caregiverToolkit",
+  "petToolkit",
+  "petGuide"
+]

Changed2 schema fields changedOct 23, 2026

addedOutput schema / properties / readingPages

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "caregiverToolkit": {
+      "format": "uri",
+      "type": "string"
+    },
+    "comparison": {
+      "format": "uri",
+      "type": "string"
+    },
+    "pickupDelivery": {
+      "format": "uri",
+      "type": "string"
+    },
+    "washFold": {
+      "format": "uri",
+      "type": "string"
+    }
+  },
+  "required": [
+    "washFold",
+    "pickupDelivery",
+    "comparison",
+    "caregiverToolkit"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "sourceUrl",
-  "publishedAt",
-  "locale",
-  "services",
-  "boundaries"
-]New value: +[
+  "sourceUrl",
+  "publishedAt",
+  "locale",
+  "services",
+  "boundaries",
+  "readingPages"
+]

First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower; the description still adds useful guarantees ('never collects personal data or creates an order') and a scope qualifier ('verified public'). It says nothing about response shape, but an output schema exists to carry that.

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 tight sentences, front-loaded with what is returned before the constraints; every clause (language, HTML pages, read-only, no PII, no order, pricing redirect) carries distinct information.

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?

With an output schema and full annotations, the description covers nearly everything needed for a single-enum read tool. The only omission is disambiguating versus get_washbodega_pickup_delivery_policy, which an agent might otherwise consider for the same question.

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?

Single optional enum parameter with 0% schema description coverage, but the description supplies the meaning: results come back in English or Spanish, mapping to the en-US/es-US enum values. That is the only semantic an agent needs here.

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?

Names a specific verb (return) and resource (verified public Wash & Fold and pickup/delivery availability plus explanatory HTML pages), and explicitly carves out rates as belonging to a sibling. An agent can tell it apart from get_washbodega_pricing 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?

Explicitly redirects rate questions to get_washbodega_pricing, which is a real routing rule. However, it does not clarify the boundary with get_washbodega_pickup_delivery_policy, a sibling whose subject overlaps with 'pickup/delivery availability'.

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

All Wash Bodega Service Discovery 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?