Skip to main content
Glama

Set up a recurring pickup

set_recurring_pickup
Destructive

Requires the connected Fold account (with a saved address and card). Creates a standing pickup — e.g. every Tuesday — at the customer's default address. Fold schedules each pickup a few days ahead; the customer can skip or pause any time. This creates real recurring orders.

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": {
      "daysOfWeek": "<daysOfWeek>"
    },
    "name": "set_recurring_pickup"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceNoDefault WASH_AND_FOLD.
frequencyNoDefault WEEKLY.
daysOfWeekYese.g. ["TUE"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the operation is not read-only, is not idempotent, and is destructive. The description adds meaningful context beyond that: account prerequisites, default-address behavior, lead time for scheduling, customer ability to skip or pause, and that real recurring orders are created.

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 short, front-loads the account prerequisite, then states the action and key behavioral facts. Each sentence contributes useful information with no filler.

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?

Given rich annotations, fully described parameters, and no output schema, the description covers prerequisites, creation behavior, scheduling lead time, and skip/pause flexibility. It is nearly complete, though it could explicitly mention how to modify or cancel the recurring series via the update sibling.

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 100%, and the schema already documents defaults for service and frequency plus an example for daysOfWeek. The description adds no parameter-level semantics beyond mentioning the customer's default address, so the baseline of 3 is appropriate.

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?

The description uses a specific verb and resource ('Creates a standing pickup') and clarifies it is for recurring orders, distinguishing it semantically from one-off booking siblings. It does not explicitly name alternatives such as book_my_pickup or update_recurring_pickup, so it falls short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides useful prerequisites ('connected Fold account with a saved address and card') and implies recurring-use cases with 'every Tuesday' and 'real recurring orders.' However, it never explicitly says when to choose this over book_my_pickup, update_recurring_pickup, or other scheduling siblings.

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