Skip to main content
Glama
Sign In
@quackai/q402-mcp

@quackai/q402-mcp

Official
by quackai-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

q402_recurring_pause

Pause an active recurring payment rule by its rule ID to temporarily halt payments until you resume it. Fully reversible; no need to re-author the rule.

Instructions

Pause an active recurring-payment rule. Takes a ruleId (from q402_recurring_list). The rule transitions to status "paused" - the cron skips it on every tick until you resume. Fully reversible via q402_recurring_resume. Use this when the user says 'pause my Friday payout' or 'hold on, stop my recurring rule for now' - gentler than cancel, no re-authoring required. Authenticated by the paid Multichain API key (same gate as create/cancel). Read q402_recurring_list first to find the matching ruleId.

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": {
      "ruleId": "<ruleId>"
    },
    "name": "q402_recurring_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleIdYesRule id from q402_recurring_list. Required.
walletIdNoOptional. Lowercased Agent Wallet address when the user holds multiple wallets. Defaults to Q402_AGENT_WALLET_ADDRESS env, then the owner's default wallet on the server.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.14

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description carries full burden. It discloses the state transition to 'paused', the cron skipping behavior, full reversibility via resume, and authentication requirements. This is comprehensive behavioral disclosure.

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 well-structured and front-loaded, but slightly redundant: it mentions ruleId provenance twice ('Takes a ruleId (from q402_recurring_list)' and later 'Read q402_recurring_list first to find the matching ruleId'). Still, every sentence carries meaningful information.

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?

For a tool with no annotations and no output schema, this description covers all necessary context: purpose, usage, behavior, reversibility, alternatives, authentication, and prerequisites. It is fully complete for an agent to select and invoke the tool correctly.

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 100%, so baseline is 3. The description adds value by specifying the source of ruleId ('from q402_recurring_list') and reinforces the prerequisite of listing first. This goes slightly beyond the schema's parameter descriptions.

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 opens with a specific verb+resource: 'Pause an active recurring-payment rule.' It clearly distinguishes this from sibling tools like q402_recurring_cancel and q402_recurring_resume by explicitly mentioning them.

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

Usage Guidelines5/5

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

Provides explicit usage scenarios ('pause my Friday payout', 'hold on, stop my recurring rule for now') and contrasts with cancel ('gentler than cancel, no re-authoring required'). Also instructs to read q402_recurring_list first to find the ruleId, giving a clear prerequisite.

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

Deploy Server

Other Tools