Skip to main content
Glama

Propose auto-recharge

autoshort_setup_auto_recharge

Propose auto-recharge with a chosen pack and monthly USD cap so future purchases skip new payment links; returns an approval URL for the owner to confirm terms and save a card.

Instructions

Propose auto-recharge so later purchases need no link: a pack and a monthly USD cap. Returns approvalUrl — the owner signs in, confirms exactly that pack and cap, and saves a card on Whop (nothing is charged then). Tell the user the pack price and the cap before sending the link. Until they finish, nothing changes. Cap: pack price to $500/month. Free.

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": {
      "pack": "<pack>",
      "monthlyCapUsd": "<monthlyCapUsd>"
    },
    "name": "autoshort_setup_auto_recharge"
  }
}

Input Schema

NameRequiredDescriptionDefault
packYes
monthlyCapUsdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag this as non-read-only, non-destructive, non-idempotent, and open-world, but the description adds genuinely new behavior: it returns approvalUrl, the owner must sign in and confirm the exact pack and cap, no charge occurs at proposal time, and nothing changes until they finish. The only gap is what happens on repeat invocation (idempotentHint=false implies duplicates are possible) and any auth/ownership requirements beyond 'the owner'.

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 the action and the payoff, then the return value, then the pre-send obligation. Dense and mostly waste-free, with only slight repetition in 'nothing is charged then' and 'Until they finish, nothing changes.'

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 two-parameter, no-output-schema tool, the description covers the return value, the approval flow, cost timing, and the cap range. Missing only edge-case behavior, such as overriding an already-active auto-recharge or how failures surface.

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 load, and it does: it defines monthlyCapUsd as a monthly USD cap, clarifies the effective floor is the pack price (schema minimum is 1), and pairs 'pack' with the quoted price the user must see. It stops short of explaining what the MICRO/STARTER/VALUE/MEGA tiers mean.

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

Purpose4/5

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

The description names a specific action (propose auto-recharge with a pack plus a monthly USD cap) and states the outcome (later purchases need no link, an approvalUrl is returned). This is clearly distinct from 'never set anything up' and from a direct purchase, though it does not name autoshort_buy_credits or get_buy_credits_url as the immediate-purchase alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: the tool is for setting up recurring purchasing so later buys skip the link, and it instructs the agent to quote pack price and cap before sending the link. There is no explicit when-not guidance or comparison to the one-off purchase / disable siblings, so the agent must infer the boundary.

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