Skip to main content
Glama
KaiCalls MCP Server

KaiCalls MCP Server

Official

Get Subscription

get_subscription
Read-onlyIdempotent

Reads a business's subscription status, plan name, and renewal or end date so you can explain what cancellation will do before changing the plan.

Instructions

Read the business's own plan: no_paid_plan, active, or canceling, with the plan name and the renewal or end date. Use before cancel_subscription to tell the owner what will happen.

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

Input Schema

NameRequiredDescriptionDefault
business_idNoBusiness ID (optional only when the token can access exactly one business).

Output Schema

NameRequiredDescriptionDefault
planNo
errorNoPresent when success is false
stateNo
statusNo
successYesWhether the tool completed successfully
manage_urlNo
period_endNo
business_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: the three possible subscription states and the fact that the date returned is either a renewal or an end date depending on state. It does not discuss permissions or token-scoping behavior, hence a 4 rather than 5.

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 return shape front-loaded and the workflow hint second. Every clause earns its place.

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?

An output schema exists, so the description needn't document the response object, yet it still summarizes the meaningful return states. For a single-optional-parameter read tool this is complete enough to call 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?

There is a single parameter and schema coverage is 100%; the schema itself documents business_id including the optional-only-when-single-business rule. The description adds nothing about the parameter, so the 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?

States a specific verb and resource ('Read the business's own plan') and enumerates the possible states (no_paid_plan, active, canceling) plus the fields returned (plan name, renewal or end date). This makes it clearly distinct from siblings such as list_subscription_history and cancel_subscription.

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?

Explicitly routes the agent: 'Use before cancel_subscription to tell the owner what will happen' names the alternative and the condition that selects this tool. The only mild gap is the absence of an explicit when-not-to-use clause, but the pre-cancellation context is unambiguous.

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