Skip to main content
Glama

Subscribe or resubscribe

amber_reactivate_subscription

Create a PayPal subscription and return an approval URL to reactivate access. Warn users to log in with their original PayPal account; no charge until approved.

Instructions

Create a PayPal subscription and return an approval URL. The user MUST open this URL in their browser to activate. Do NOT use if the user just wants to manage an existing subscription -- use amber_manage_subscription instead.

First-time: 90-day free trial, then $2.99/month. Returning: preserves remaining free days, or bills immediately if expired. Warn the user to log in with the SAME PayPal account they originally signed up with.

No charge until the user approves. Returns code: already_active if active, code: deletion_scheduled if deletion is pending. Each call creates a NEW pending subscription with its own approval URL, so give the user the latest one. Approving one cancels any other active subscription on the same account, so an older link approved by mistake cannot bill twice.

Errors: creation_failed (PayPal would not create the subscription; nothing was charged and retrying is safe).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
statusYesAlways `approval_needed`: a subscription was created and is waiting for the user to approve it at PayPal. Nothing is charged and nothing is active until they do.
messageYesA human-readable summary, including the approval link the user has to open.
approval_urlYesURL the user must open to approve the subscription. ALWAYS share this URL with the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "approval_url": {
      +      "description": "URL the user must open to approve the subscription. ALWAYS share this URL with the user.",
      +      "type": "string"
      +    },
      +    "message": {
      +      "description": "A human-readable summary, including the approval link the user has to open.",
      +      "type": "string"
      +    },
      +    "status": {
      +      "const": "approval_needed",
      +      "description": "Always `approval_needed`: a subscription was created and is waiting for the user to approve it at PayPal. Nothing is charged and nothing is active until they do.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "approval_url",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing pricing/trial terms, that no charge occurs before approval, that each invocation mints a new pending subscription and invalidates older links, that approving one cancels other active subscriptions on the account, and specific status/error codes (`already_active`, `deletion_scheduled`, `creation_failed`) with retry safety. The non-idempotent behavior is explicitly justified by 'each call creates a NEW pending subscription', which aligns with `idempotentHint: false`.

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-loads the action and the hard requirement, then layers first-time/returning behavior, status codes, and errors in a scannable order. It is dense with genuinely useful facts, though a few lines (the double-billing explanation) are longer than needed for an agent to act correctly.

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?

Despite an output schema existing, the description usefully pre-declares the branches an agent must handle (`already_active`, `deletion_scheduled`, `creation_failed`), plus the human-in-the-loop browser step that annotations alone would never convey. For a zero-param, open-world, non-idempotent mutation, 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?

The tool takes zero parameters, so the 4 baseline applies; there is no input surface for the description to clarify further. The description correctly spends its words on flow branching and outcomes rather than inventing parameter details.

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?

Opens with a specific verb and resource plus the concrete return artifact: 'Create a PayPal subscription and return an approval URL.' It immediately distinguishes itself from `amber_manage_subscription`, so an agent can route between the two 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('first-time' vs 'returning' flows), explicit when-not ('Do NOT use if the user just wants to manage an existing subscription'), and names the sibling alternative to use instead. It also states the required post-call user action (must open the URL in a browser) and the account-matching warning.

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