Skip to main content
Glama

Pause, resume or cancel a recurring pickup

update_recurring_pickup
DestructiveIdempotent

Requires the connected Fold account. action: pause (optionally until a YYYY-MM-DD date), resume, or cancel a recurring pickup (recurringId from get_my_account).

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": {
      "recurringId": "<recurringId>",
      "action": "<action>"
    },
    "name": "update_recurring_pickup"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
pauseUntilNoYYYY-MM-DD (pause only). Omit to pause until resumed.
recurringIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is carried structurally. The description adds the account-connection prerequisite, but never says that cancel is irreversible or what state a pickup is left in after pause/resume, which is the main behavioral thing an agent would want before choosing 'cancel'.

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?

One compact sentence with the prerequisite front-loaded and the operations enumerated; nothing is wasted. It is slightly dense – the prerequisite and the action semantics are compressed into a single clause chain – but it reads cleanly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description could say what comes back after a pause/resume/cancel, and it does not. Combined with the missing irreversibility note on cancel, this covers the essentials for invocation but leaves the agent guessing about results and consequences.

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?

Schema coverage is only 33% (recurringId is undocumented in the schema), and the description compensates by stating where recurringId comes from (get_my_account) and that pauseUntil is optional and date-formatted for pause only. That is real added meaning beyond the schema.

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?

States a specific resource (recurring pickup) and the three concrete operations (pause/resume/cancel), which cleanly separates it from set_recurring_pickup, reschedule_order and cancel_order. The title and body agree, so an agent can route on purpose alone.

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?

"Requires the connected Fold account" sets a prerequisite, and pointing to get_my_account for recurringId tells the agent how to obtain a required input. No explicit when-not or alternative routing (e.g. cancel_order vs this) is given, so it stops short of a 5.

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