Skip to main content
Glama
KaiCalls MCP Server

KaiCalls MCP Server

Official

Cancel Subscription

cancel_subscription
DestructiveIdempotent

Cancels a business's plan when the owner requests it, stops future charges, keeps access until the paid period or trial ends, and lets undo=true reverse a pending cancellation.

Instructions

Cancel the business's plan when the owner asks to. The plan stays on until the end of the paid period (or trial) and is never charged again; a past-due plan ends now. Pass undo=true to keep a plan whose cancel has not taken effect yet. Requires the current owner role. Confirm with the owner before calling.

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": "cancel_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
undoNotrue keeps the plan: undoes a cancel that has not taken effect yet.
detailNoThe owner's own words.
reasonNoWhy the owner is cancelling. Required to cancel (not for undo): ask the owner, and pass other with their words in detail if none fits.
business_idNoBusiness ID (optional only when the token can access exactly one business).

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when success is false
messageNo
outcomeNo
successYesWhether the tool completed successfully
manage_urlNo
business_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already flag destructive=true and idempotent=true, but the description goes well beyond them: it discloses the exact timing effect (access persists through the paid period or trial, no further charges, past-due ends immediately), the undo window, and the authorization requirement. That is precisely the context an agent needs before performing a destructive billing mutation.

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?

Compact and front-loaded: what it does, what happens to the plan, then the undo exception, then preconditions. Every clause carries distinct information with no filler or repetition.

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 destructive four-parameter tool with an output schema already documenting return values, the description covers everything an agent needs: timing consequences, the undo reversal path, permission requirements, and the confirm-before-calling etiquette. Nothing material is missing.

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 description coverage is 100%, so the schema already defines undo, reason, detail, and business_id. The description still adds operative meaning by framing undo as the recovery path for a cancel that has not taken effect, tying parameter choice to the described state machine. It does not restate the reason enum values or the optional-business_id rule, so there is some room left.

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 precise verb and resource ('Cancel the business's plan') and adds scope qualifiers — owner-initiated, undo path, past-due handling — that let an agent distinguish it from read-only siblings like get_subscription or list_subscription_history without opening either schema.

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?

Gives explicit when-to-use ('when the owner asks to'), a prerequisite ('Requires the current owner role'), a safety instruction ('Confirm with the owner before calling'), and the alternative path (undo=true for a not-yet-effective cancel). It stops short of routing the agent to a sibling tool for pre-checking subscription state, so it is strong but not complete.

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