Skip to main content
Glama

Wash Bodega Service Discovery

Get Wash Bodega pricing

get_washbodega_pricing
Read-onlyIdempotent

Return verified public pricing and minimums for Wash & Fold or pickup/delivery. Read only; specialty and commercial quotes are excluded.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service": "<service>"
    },
    "name": "get_washbodega_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoen-US
serviceYes

Output Schema

NameRequiredDescriptionDefault
nameYes
unitYes
ratesYes
localeYes
statusYes
serviceYes
currencyYes
minimumLbYes
pickupFeeYes
sourceUrlYes
verifiedAtYes
deliveryFeeYes
publishedAtYes
taxIncludedYes
washFoldBagYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / taxIncluded
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / washFoldBag
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "biWeeklySub": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "minBagsPerMonth": {
      +              "type": "number"
      +            },
      +            "monthlyMinimum": {
      +              "type": "number"
      +            },
      +            "perBag": {
      +              "type": "number"
      +            },
      +            "rollover": {
      +              "type": "boolean"
      +            }
      +          },
      +          "required": [
      +            "perBag",
      +            "minBagsPerMonth",
      +            "monthlyMinimum",
      +            "rollover"
      +          ],
      +          "type": "object"
      +        },
      +        "channels": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "closureRule": {
      +          "type": "string"
      +        },
      +        "maxLb": {
      +          "type": "number"
      +        },
      +        "oneTimePerBag": {
      +          "type": "number"
      +        },
      +        "weeklySub": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "minBagsPerMonth": {
      +              "type": "number"
      +            },
      +            "monthlyMinimum": {
      +              "type": "number"
      +            },
      +            "perBag": {
      +              "type": "number"
      +            },
      +            "rollover": {
      +              "type": "boolean"
      +            }
      +          },
      +          "required": [
      +            "perBag",
      +            "minBagsPerMonth",
      +            "monthlyMinimum",
      +            "rollover"
      +          ],
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "maxLb",
      +        "closureRule",
      +        "oneTimePerBag",
      +        "biWeeklySub",
      +        "weeklySub",
      +        "channels"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "sourceUrl",
      -  "publishedAt",
      -  "locale",
      -  "service",
      -  "name",
      -  "status",
      -  "currency",
      -  "unit",
      -  "minimumLb",
      -  "rates",
      -  "pickupFee",
      -  "deliveryFee",
      -  "verifiedAt"
      -]New value: +[
      +  "sourceUrl",
      +  "publishedAt",
      +  "locale",
      +  "service",
      +  "name",
      +  "status",
      +  "currency",
      +  "unit",
      +  "minimumLb",
      +  "rates",
      +  "pickupFee",
      +  "deliveryFee",
      +  "taxIncluded",
      +  "washFoldBag",
      +  "verifiedAt"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is fully covered. The description adds useful scope context ("verified public", minimums included, specialty/commercial excluded), but says nothing about freshness of pricing or response shape beyond 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, scope first and exclusions second, with no redundant restatement of the name or annotations. Every clause carries 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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. Given the simple two-parameter, enum-only input, the description is nearly complete; only the locale parameter's effect is left unaddressed.

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 description coverage is 0%, so the description must carry the param burden. It maps naturally onto the `service` enum values (wash-fold, pickup-delivery), but the `locale` parameter and its en-US/es-US effect on returned pricing are never mentioned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Return verified public pricing and minimums") and constrains scope to Wash & Fold or pickup/delivery. The exclusion of specialty and commercial quotes further sharpens the boundary, though no sibling tool is named for contrast.

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?

Clear context for when to call: public pricing and minimums for the two listed service types. It also states when not to rely on it (specialty and commercial quotes are excluded), but does not point the agent to an alternative for those cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources