Skip to main content
Glama

Update laundry preferences

update_care_preferences
DestructiveIdempotent

Requires the connected Fold account. Saves standing laundry preferences applied to every future order: detergent (eco_unscented = unscented eco, free & clear, the default; or tide), waterTemp (mixed = standard: colors cold, whites warm, the default; cold; warm; hot), and specialInstructions (free text the facility sees on every order, max 500 chars; pass an empty string to clear). Only the fields you pass change.

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": "update_care_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
detergentNo
waterTempNo
specialInstructionsNoe.g. "hang-dry activewear, no fabric softener". Empty string clears.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description explains the key behavioral effects: preferences persist across future orders, only passed fields change, defaults are defined, and an empty string clears specialInstructions. This gives an agent enough context to understand the mutation and its destructive clearing behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the account requirement and purpose, and every sentence carries useful information. It is dense but not bloated; slightly clearer formatting of the parenthetical enum definitions would improve readability.

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?

With no output schema and three optional parameters, the description covers the account prerequisite, persistence scope, partial-update semantics, defaults, and clearing behavior. Nothing essential for correctly invoking this mutation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, so the description must compensate, and it does: it explains all three parameters, defines enum meanings and defaults for detergent and waterTemp, states the 500-character limit, and documents empty-string clearing for specialInstructions.

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 states a specific verb and resource: it saves standing laundry preferences applied to every future order. It clearly distinguishes these preferences from schedule-related siblings by emphasizing detergent, water temperature, and special instructions rather than pickup timing.

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?

It gives clear usage context: this is for standing preferences that apply to every future order, and it requires a connected Fold account. It does not explicitly name alternatives such as per-order instructions or contrast with update_recurring_pickup, so it stops short of full when/when-not guidance.

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