Recurly MCP Server and API by Cotlet

Cancel subscription in Recurly

recurly_cancel_subscription

Read-onlyIdempotent

Cancel subscription in the user's own Recurly account from ChatGPT, Claude or any AI agent. Returns how to do it in Recurly step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Recurly Cloud Browser. Recurly's official API: Yes, Recurly has a full REST API for accounts, subscriptions, invoices, transactions and coupon redemptions (checked 14 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recurly_cancel_subscription"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description reinforces this in plain language by stating it 'opens nothing by itself' — valuable because the tool name implies a destructive action. It also discloses the shape of the output (step-by-step screens, buttons, fields). It does not mention caching, freshness, or any failure mode.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core instruction is compact and mostly front-loaded, but 'from ChatGPT, Claude or any AI agent' is filler and the closing sentence about Recurly's official REST API ('checked 14 Oct 2026') is irrelevant to invoking a zero-parameter guidance tool. Those sentences cost readability without helping selection or invocation.

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?

For a no-parameter, no-output-schema tool with rich annotations, the description covers what is returned (step-by-step instructions) and the required follow-up workflow (cotlet_browser_* tools). The only missing piece is any hint about coverage limits or prerequisites for the user's Recurly session.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the schema needs no compensation. The description correctly implies no inputs are required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause 'Cancel subscription in the user's own Recurly account' reads like the tool performs the cancellation, and only the second clause ('Returns how to do it in Recurly step by step … and opens nothing by itself') corrects that to a guidance-only tool. The resource is named, but the verb is muddled, and no sibling such as recurly_change_subscription is distinguished.

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?

It gives a concrete usage path: call this to get step-by-step screens/buttons/fields, then execute with the cotlet_browser_* tools in the Recurly Cloud Browser. That is a real handoff to an alternative tool set. It stops short of stating when NOT to use it or how it differs from the other recurly_* mutation-adjacent tools.

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

All Recurly MCP Server and API by Cotlet 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?