The River

Stop a recurring buy (unsigned tx)

stop_recurring_buy

Read-only

One transaction: withdraw what the plan has not spent and what it bought to the wallet, then remove it. Returns unsigned transactions for the user to sign in their own wallet, in order; nothing is sent or signed here.

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": {
      "chainId": "<chainId>",
      "owner": "<owner>",
      "planId": "<planId>"
    },
    "name": "stop_recurring_buy"
  }
}

Input Schema

Name	Required	Description
`owner`	Yes	0x... address
`planId`	Yes	The plan's order hash, 0x... 32 bytes
`chainId`	Yes	8453 Base, 4663 Robinhood Chain

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the annotations, the description discloses the critical behavior: a multi-step operation packaged as one call, returned as unsigned transactions that must be signed in order, with nothing signed or sent server-side. That resolves the apparent tension with readOnlyHint=true by making clear the tool only builds transactions. It does not cover what multiple transactions may be returned or what happens if the plan is already closed.

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?

Two sentences, zero filler, with the core action and its outcome front-loaded before the signing caveat. Every clause carries information an agent needs.

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?

No output schema exists, and the description compensates by explaining the return value (unsigned transactions, ordered, to be signed by the user). For a three-parameter mutation-planning tool that is nearly complete; only failure modes and the case of an already-stopped plan are unaddressed.

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%, with owner, planId and chainId (including an enum with chain names) fully documented in the schema. The description adds no parameter-level meaning, so the baseline 3 applies.

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 names a specific verb and resource (stop a recurring buy plan) and describes the exact mechanism: withdraw unspent funds and purchased assets, then remove the plan. It is clearly distinct from siblings like cancel_limit_order or start_recurring_buy by the nature of the operation, but it never explicitly names or contrasts those alternatives.

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?

Usage is only implied by the tool name and the mechanism described; there is no explicit statement of when to choose this over cancel_limit_order or withdraw, and no prerequisites (plan must exist and be active, caller must be the owner) are stated. An agent can infer the context but must reason about it rather than read it.

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

All The River tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?