Skip to main content
Glama

Buy a plan (payment link)

subscribe

Creates a LavaTop payment for a monthly plan (trial, start, growth, scale; prices in list_plans) and returns its payment_url and order id. Confirm the plan, price and currency with the user first. GIVE THE LINK TO THE USER: a person pays on LavaTop's page by card, SBP or PayPal (an agent cannot). Currency is also the method: RUB — Russian cards and SBP; USD — foreign cards, PayPal, Apple Pay (Russian cards pay only in RUB). A USD link lives 15 minutes, a RUB link 24 hours. A plan not yet sold online answers plan_unavailable: the user writes to support. Then poll get_payment_status every 15-30 s until paid; the plan's credits and briefs arrive with the payment and renew monthly until cancel_subscription. [REST: POST /api/billing/checkout]

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": {
      "plan": "<plan>"
    },
    "name": "subscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYes
currencyNoUSD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / plan / enum
      Previous value: -[
      -  "start",
      -  "growth",
      -  "scale"
      -]New value: +[
      +  "trial",
      +  "start",
      +  "growth",
      +  "scale"
      +]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare it is a non-read-only, non-idempotent, non-destructive, closed-world write; the description goes well beyond that with link TTLs (15 min USD vs 24 h RUB), accepted payment methods per currency, the plan_unavailable error, and the recurring credit delivery until cancel_subscription. These are operational facts an agent cannot derive from the annotation block or schema.

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

Conciseness4/5

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

Front-loaded with what the tool does and returns, and nearly every sentence carries unique operational information; the capitalized instruction flags the critical hand-off step. It is dense and long for a two-parameter tool, and the trailing REST endpoint note is of marginal value to an agent.

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 two-parameter, no-output-schema tool the description covers return values, error handling, link expiry, and the required follow-up call. Nothing needed to invoke it correctly or to interpret the result 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 coverage is 0%, so the description must carry the meaning — and it does for currency, tying RUB to Russian cards/SBP and USD to foreign cards/PayPal/Apple Pay and to different link lifetimes. It also points to list_plans for plan pricing, though it does not explain how the four plan tiers differ.

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 — creates a LavaTop payment for a monthly plan — and names the exact return values (payment_url and order id). It also distinguishes itself from siblings by pointing to list_plans for prices and get_payment_status for follow-up polling.

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 says to confirm plan, price and currency with the user first, that the agent must hand the link to the human rather than pay, and to poll get_payment_status every 15-30 s until paid. It names the alternative flow (cancel_subscription ends renewal) and the failure path (plan_unavailable → support).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources