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

@quackai/q402-mcp

Official
by quackai-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

q402_recurring_cancel

Cancel an active recurring-payment rule on an Agent Wallet using its rule ID. Stops future payments immediately and handles already-cancelled rules idempotently.

Instructions

Cancel an active recurring-payment rule on the Agent Wallet. Takes a ruleId (from q402_recurring_list). Cancel is immediate - the rule will not fire again. Authenticated by the configured Multichain API key. Idempotent: cancelling an already-cancelled rule returns 409 with a clear message. Use this whenever the user says 'stop my recurring payment to X' - call q402_recurring_list first to find the matching ruleId, then call this with that id.

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_cancel"
  }
}

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.5/5.0
Behavior5/5

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

With no annotations, the description carries full burden. It discloses immediate cancellation, that the rule will not fire again, authentication via the Multichain API key, and idempotency with a 409 response for already-cancelled rules. This is rich behavioral context.

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?

Four sentences pack all essential info: action, parameter source, behavior, auth, idempotency, and usage workflow. No unnecessary words.

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?

Given no output schema, the description covers purpose, precondition (call list first), behavioral details, authentication, and an error case. It is self-contained and sufficient for an agent to select and invoke correctly.

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 coverage is 100% with clear parameter descriptions. The description only repeats the ruleId source (from q402_recurring_list) and adds no new parameter-specific meaning beyond what the schema already provides. Baseline 3 applies.

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 clearly states 'Cancel an active recurring-payment rule on the Agent Wallet,' with a specific verb and resource. It also distinguishes from siblings by emphasizing immediate cancellation, unlike pause/resume.

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?

Explicitly instructs when to use: 'Use this whenever the user says stop my recurring payment to X' and provides a workflow to call q402_recurring_list first. However, it doesn't mention alternatives like pause or resume, so it lacks explicit exclusion guidance.

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